Log in

View Full Version : Dell Axim Internet Explorer Bad Request


fj900
02-14-2003, 02:46 AM
I have recently upgraded my 2 1/2 year old IPAQ for a Dell Axim. I have found that on the Dell I have had several web sites I normally need to use respond with the message BAD REQUEST. For anyone interested in purchasing the AXIM please be aware this is a known problem. Please see the following messase as posted on the Dell Forum board. If anyone knowns of any work arounds please let me know. I have already tried using regking to simulate pocket explorer as internet explorer ver 5 but this had no effect.

http://forums.us.dell.com/supportforums/board/message?board.id=dellpda&message.id=13212

Pocket IE Bad Request problem identified!

Sorry for the technical nature of this message.

With the help of a fellow user with an iPaq (Larry H) I have figured out WHY the Axim cannot visit certain sites with PocketIE. The reason is the following line sent by pocket IE in the initial "GET" packet:

UA-CPU: Intel® PXA250

The reason for the problem is the ® character. If that character is present certain web servers will return with the bad request error. I have narrowed it down to this character by writing a custom app that sends a GET packet to http://wireless.cnn.com with custom headers. If the ® is present a "Bad request" is received, if the ® is ommited the server returns the correct page.

So far the servers that have a problem with the ® symbol have identified themselves as: Server: Netscape-Enterprise/4.1. I have only checked a couple sites so I don't know whether the problem is with all instances of this specific server, nor whether it is limited to servers of that type.

FWIW the packet sniffer I use (EtherReal) ALSO doesn't like GET packets with a field that contains the ®, so perhaps IE is violating the standard for http GET requests? I don't know.

Now with the problem narrowed down the question is HOW to remedy it. So far I haven't figured out how to get PocketIE to modify the UA-CPU line it sends. I plan to look through the registry, but I doubt that line is variable, chances are it's hard coded at compile time by Microsoft, in which case it's up to them to fix it, and for Dell to pass it on.

The interesting thing is do other PDAs based on the Intel PXA250 send the same header string?

Anyways if anyone out there has any further questions please let me know, let's hope Dell is listening. TTYL


So that's why mobile.fedex.com wont work!!!!!!!!!

Pony99CA
02-14-2003, 03:44 AM
Pocket IE Bad Request problem identified!

Sorry for the technical nature of this message.

With the help of a fellow user with an iPaq (Larry H) I have figured out WHY the Axim cannot visit certain sites with PocketIE. The reason is the following line sent by pocket IE in the initial "GET" packet:

UA-CPU: Intel® PXA250

The reason for the problem is the ® character. If that character is present certain web servers will return with the bad request error. I have narrowed it down to this character by writing a custom app that sends a GET packet to http://wireless.cnn.com with custom headers. If the ® is present a "Bad request" is received, if the ® is ommited the server returns the correct page.

So far the servers that have a problem with the ® symbol have identified themselves as: Server: Netscape-Enterprise/4.1. I have only checked a couple sites so I don't know whether the problem is with all instances of this specific server, nor whether it is limited to servers of that type.

FWIW the packet sniffer I use (EtherReal) ALSO doesn't like GET packets with a field that contains the ®, so perhaps IE is violating the standard for http GET requests? I don't know.

Now with the problem narrowed down the question is HOW to remedy it. So far I haven't figured out how to get PocketIE to modify the UA-CPU line it sends. I plan to look through the registry, but I doubt that line is variable, chances are it's hard coded at compile time by Microsoft, in which case it's up to them to fix it, and for Dell to pass it on.

Good catch on the cause of the problem! :-)

Howver, I don't think it's a Microsoft issue. Each OEM probably has to put their own string in there because Microsoft doesn't know which processor the OEM will be developing for. That would explain why Dell might have this problem while HP XScale iPAQs might not.

Steve