* at 30/06 10:18 +0800 Gunther Birznieks said:
>
> At 09:06 AM 6/30/00 +0700, Edwin Pratomo wrote:
> >
> >this doesn't seem to be aware of either WAP browsers or the emulators.
> >A typical usage of this is to return WML pages if the request comes from
> >a WAP browser, otherwise return html pages.
> >
> >Regards,
> >Edwin.
>
> That is a different method.
>
> The fact is that you can't really easily tell if a browser is WAP or not
> from the useragent because there are new ones coming out every day... every
> phone and potentially every gateway is a user agent (the gateway may add
> its own details since it is the client that is actually going to the web
> server).
>
> It is part of the HTTP standard to negotiate content. So if a WAP browser
> can't digest HTML, then text/html will not be among the content types that
> it accepts I suspect.
We've had some success by using the HTTP_ACCEPT header and plain old
apache redirects for WAP. We did try UA sniffing but as you say the
sheer number of new browsers coming out meant we were changing stuff
almost daily.
Struan
--
Struan Donald
mailto:[EMAIL PROTECTED]
Code Flunky, 365 Plc.
http://www.365corp.com/
