Re: ASP detection for wireless devices
by "Frank Boumphrey" <bckman(at)ix.netcom.com>
|
| Date: |
Wed, 14 Nov 2001 22:47:45 -0500 |
| To: |
<hwg-techniques(at)hwg.org>, "Robin Liston" <rliston(at)home.com> |
| References: |
home |
| |
todo: View
Thread,
Original
|
|
ASP allows you to read the headers that the client sends back, and in the
headers is a description of the OS being used which is in the
request.ServerVariables collection.
Of the top of my head try:
<%
for each key in Request.ServerVariables
response.write key & ": _ " & Request.ServerVariables(key) & "<br>"
next
%>
This will
If I remember rightly you will find it under the HTTP_USER_AGENT key, but
the above script will return everything and you can sort out what you want.
HTH
Frank
----- Original Message -----
From: "Robin Liston" <rliston(at)home.com>
To: <hwg-techniques(at)hwg.org>
Sent: Wednesday, November 14, 2001 10:28 AM
Subject: Re: ASP detection for wireless devices
> It's not cheap but Cyscape's BrowserHawk claims to do this.
> http://www.cyscape.com/
>
> I use it for other detection reasons, but it is suppose to detect WAP and
> PDA devices.
>
> HTH
>
> At 09:15 AM 11/13/2001 -0800, you wrote:
> >Hello,
> >
> >I'm looking for a nice, easy solution for device detection for our web
> >site. We're currently using Active Perl to detect the user's device when
> >they come to our page, and then we redirect Wireless Device users and PC
> >users to different pages, depending on what they're using.
> >
> >Does anybody have a way to duplicate this functionality in ASP? I've got
a
> >few ideas for how it might be done, but I'd like to see what people are
> >using to do this, if anybody is.
> >
> >Thanks!
> >Rebecca
> >http://www.nerdygirl.com
> >
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> 10 years ago I had men fighting over me...
> now they just fight with me.
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
HWG hwg-techniques mailing list archives,
maintained by Webmasters @ IWA
This page is part of a preserved archive of archives.hwg.org. The site is no longer active and its content is not maintained. For enquiries about this archive, write to archive(at)iwanet.org.