Stipe, You're right. Relative URL in the page will lead to serious problem. Do you have any solutions? Maybe we should modify the response page, tell the wap terminal the base URI (or host) in the WML/XHTML document.
Best Regards, Guanghua Hou ----- Original Message ----- From: +ACI-Stipe Tolj+ACI- +ADw-tolj+AEA-wapme-systems.de+AD4- To: +ACI-Rene Kluwen+ACI- +ADw-rene.kluwen+AEA-chimit.nl+AD4- Cc: +ACI-ghhou+ACI- +ADw-ghhou+AEA-utstar.com+AD4AOw- +ADw-devel+AEA-kannel.org+AD4- Sent: Thursday, November 27, 2003 8:20 AM Subject: Re: HTTP redirect +AD4- Rene Kluwen wrote: +AD4- +AD4- +AD4- +AD4- -----BEGIN PGP SIGNED MESSAGE----- +AD4- +AD4- Hash: SHA1 +AD4- +AD4- +AD4- +AD4- If you mean a relative URL in the Location: header. +AD4- +AD4- Then this is something against HTTP specs. One should not use them. +AD4- +AD4- Even though almost all browsers do prepend the original http-path if you do +AD4- +AD4- send them. +AD4- +AD4- nop, the point is different. +AD4- +AD4- Kannel wapbox does the Location following (hence redirection) +AD4- transparently to the WAP user agent. Hence relative URLs within the +AD4- WAP deck would result to address resources that are ment to be on a +AD4- previously redirected URL. And there is where we +ACI-may+ACI- run into +AD4- problems. +AD4- +AD4- Stipe +AD4- +AD4- mailto:tolj+AEA-wapme-systems.de +AD4- ------------------------------------------------------------------- +AD4- Wapme Systems AG +AD4-
