> Our Kannel WAP gateway is exhibiting some strange behaviour > when visiting > a few sites. (Notably wap.ft.com). > > The request gets sent off fine, and Kannel sees an HTTP 302 status > message, however it never seems to get the headers or the > Location header > and eventually the WAP device just times out.
I've looked specifically at wap.ft.com. The problem is that the HTTP headers coming back with the 302 indicate a content length of 10, but there's no body available for reading. Kannel does'nt treay this as a valid transaction and just returns, with no indication of an error. I'll have to put in some HTTP header dumps to confirm the debugger analysis, but that's what it looks like to me.
