Mobile clients identification?

Hi,

Are there any module can detect mobile clients (popular, such as Nokia
handset, iphone ect) and redirect/rewrite to another set of pages?

Thanks.

Re: Mobile clients identification?

On Thu, 17 Jan 2008 18:55:04 -0800 (PST), howa
wrote:

>Hi,
>
>Are there any module can detect mobile clients (popular, such as Nokia
>handset, iphone ect) and redirect/rewrite to another set of pages?
>
>Thanks.

Check the request headers, all WML/WAP traffic comes via
gateways. The clients don't connect to your httpd
themselves.
--
( Kees
)
c[_] Positive: Mistaken at the top of one's voice. (#82)

Re: Mobile clients identification?

On 1月19日, 上午2時56分, Kees Nuyt wrote:
> On Thu, 17 Jan 2008 18:55:04 -0800 (PST), howa

> Check the request headers, all WML/WAP traffic comes via
> gateways. The clients don't connect to your httpd
> themselves.
> --

Why not?

It is common to connect without gateway nowsday,

say m.yahoo.com or google.com/m via my Nokia WiFi-enabled handset or
even Iphone

Re: Mobile clients identification?

Hi Howa,

There seems to be no one with experience in this field who
wants to post, so I'll try once more ;)

On Sat, 19 Jan 2008 04:52:03 -0800 (PST), howa
wrote:

>On 1?19?, ??2?56?, Kees Nuyt wrote:
>> On Thu, 17 Jan 2008 18:55:04 -0800 (PST), howa
>
>> Check the request headers, all WML/WAP traffic comes via
>> gateways. The clients don't connect to your httpd
>> themselves.
>
>Why not?
>
>It is common to connect without gateway nowsday,
>
>say m.yahoo.com or google.com/m via my Nokia WiFi-enabled handset or
>even Iphone

I was only talking about WML/WAP. They require a gateway.
Addressing html/http is not impossible if a device is only
WAP capable, some gateways will try to convert html/http
to wml/wap vice versa.

But apparently you are talking about mobile devices that
are more like "pocket PC's" that happen to be able to make
phone calls as well, or PDAs.
Indeed they (often) communicate more or less directly. In
that case you only have the User-Agent header.
So, my advice stays the same, the headers is all you have,
analyse them and redirect accordingly.

Google for: mobile device browser recognize
That returns 139000 hits. The first page already contains
a PHP example, and a commercial product.
Of course adding keywords will help you focus on what
you're looking for.

http://css-discuss.incutio.com/?page=HandheldStylesheets
seems a nice starter.

HTH
--
( Kees
)
c[_] What boots up must come down. (#313)