| X-wap profile header |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through September 22, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| David Tapuska New member Username: Dftapusk Post Number: 3 Registered: 04-2004 |
Reading the specification WAP-248-UAProf-20011020-a it doesn't appear that the Now WAP proxy is following section 9.2.3.3 with respect to transmitting the profile headers as x-wap-profile headers. I am wondering if this is an oversight or is done on purpose. When the profile-diff header is set; the proxy doesn't appear to be forwarded as any header at all. Can you guys comment on the lack of conformance ? | |||
| Kent Williams Moderator Username: Kent Post Number: 121 Registered: 10-2003 |
Hi David, I would say that the fact that "Profile:" is not translated to "x-wap-profile:" is an oversight. We pass through the UAProf URL in a "Profile:" header, because we had observed that behaviour in other gateways. (Also pre-WAP 2.0 specs did not define this "x-wap-" prefix.) It's a minor issue for us to change this to "x-wap-profile:". (Or most likely, what we would do is include both "Profile:" and "x-wap-profile:" because we would not want to break anything for current applications that rely on the "Profile:" header. Although I would expect that most apps are now looking for "x-wap-profile:" as it is generated by WTCP/WHTTP clients.) If you have an application need for this, then I would suggest that you e-mail wap@now.co.uk, and we can send you an update. Regarding the profile-diff headers, you are correct, we do not forward them from WSP clients. Have you seen any WSP clients that generate these headers? (I have seen other gateways, such as the Ericsson gateway, which generate profile-diff headers that were NOT present in client requests.) -Kent | |||
