Quantcast
Channel: Silk Performer
Viewing all articles
Browse latest Browse all 4084

Wiki Page: If I use the WapHeaderAdd function to set a request header, why does the returned value get split into different strings?

$
0
0
This issue was resolved in Silk Performer 7.0. The reason for the issue is that the value parameter of your header contains a colon (:) , and as a result SilkPerformer will return more than one string.  Please see the example below to illustrate this behaviour. EXAMPLE: If you use the code: WapSetHttpHeader("Accept-Language: en\r\n" "Accept-Charset: utf8\r\n" "user-agent: Openwave/1.0 (04.73)\r\n" "profile: http://10.1.1.1:8080/bal.wml"); noting the : in http://10.1.1.1:8080/bal.wml, then the log file will show the profile split into three sections as shown below. Prepare request shows: [offset= 89] 0xB5: Profile: http [offset= 95] 0xB5: Profile: \10.10.10.10 [offset=109] 0xB5: Profile: 8080\index.wml However if you use the following code to set the header: WapSetHttpHeader("Accept-Language: en\r\n" "Accept-Charset: utf8\r\n" "user-agent: Openwave/1.0 (04.73)\r\n" "profile: http;//10.1.1.1;8080/bal.wml"); The log file will show the profile returned as one string, as shown below: Prepare request shows: [offset= 89] 0xB5: Profile: http;\10.10.10.10;8080\index.wml This was resolved in Silk Performer 7.0.

Viewing all articles
Browse latest Browse all 4084

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>