Why does a normal HTTP 302 redirect not work in WAP?
The truth is that it does. The crucial detail is the server side script language, or rather the interaction between the server side script language and the web server. The so called 302 Found HTTP response basically means that the web server tells the user agent that the resource may be found elsewhere, temporarily. Some web servers happen to add a Content-type: to the response even if there is no content. By default the Content-type: is in normal circumstances text/html. Actually, the HTTP specifications on “302 Found” say that the web server, unless the request method was HEAD and not GET, should also send a body containing a short message for the (human) user saying that the location has changed. In WML‘s case, the short message must obviously be a full WML deck with one card. If the gateway/browser fully supports a redirect, the message will not be shown. If it doesn’t, the user will have to manually follow the link to the new location. This is crucial if your script may output any
