| Problems with headers not being handled by NowWAP. |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through October 01, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Magnus Krampell New member Username: Magnusk Post Number: 7 Registered: 10-2005 |
Hi We have some problems when testing our implementation of a WAP stack: 1) The GW is not able to convert/let through the headers "Cache-Control: no-store", "Pragma: no-cache" and "Etag: ". This is a serious error which prevents testing cache control with this GW. 2) A test case uses the header "Expires: 0" which by the GW is translated to the current time stamp, whereas we treat it like 1970-01-01 00:00. This makes a test case fail. 3) The GW will not let the header "X-Vodafone-Content: portal" through. This means no test cases regarding Operator Cache can be run using this GW. We use the WTLS version of NowWAP 2.58. Are any of these problems related to a configuration? Is there a manual where ALL configuration options are described? I have asked some questions here and have on some occations been given configurations that are not described in the manual.... regards, /Magnus | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6568 Registered: 10-2002 |
Hi Magnus, I need to run these issues by one of my colleagues, and give him a chance to review. Just to make sure that I understand, all of the issues that you mention above are with regard to response headers, correct? -bn | |||
| Magnus Krampell New member Username: Magnusk Post Number: 8 Registered: 10-2005 |
Yes, that is my understanding too. /Magnus | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6569 Registered: 10-2002 |
Hi Magnus, I'm back with information. Historically we've been very selective about which response headers are returned back to the client because of older phones that didn't support segmentation ... meaning that we needed to keep the response size as small as possible in order to maximize what content could be supported. That said, those older phones (think Nokia 7110) are probably retired by now. So ... 1.) We can add support for those response headers. (Note that normally, you would use Cache-Control: no-cache to indicate that the page should not be cached.) 2.) That is a bug that we will fix. Expires: 0 should be translated to a date that is clearly in the past. 3.) "X-" headers were filtered out for response size reasons that I mentioned earlier. But in the modern age, we see no reason to continue to filter them, so we will make modifications to allow all "X-" headers to be forwarded. I'm going to send you an update via e-mail. -bn | |||
