For the techies in my life...
Mar. 23rd, 2007 09:18So, does anyone know of a network security thing-y that watches URLs and kills any attempt at browsing if the URL gets above a certain length or contains characters that have been URLEncoded?
One of our clients is threatening to tear up their contract unless we can fix that problem, or find a workaround for it...
One of our clients is threatening to tear up their contract unless we can fix that problem, or find a workaround for it...
First step is identifying the cause, and I'm flummuxed. When performing a vehicle search, the URL is about 250 characters long. When you select page 2, it jumps to 671 characters long - that's valid for our system by the way, and none of our other customers have reported a problem.
Only the computers at this one dealership have this symptom: page 1 displays fine. Page 2 returns a blank screen. Not even the obligatory <html></html> in the source that IE seems to toss in just for fun when there's nothing to display. It just dies.
I'm starting by moving some processing out of the querystring and into a text file or the database. That'll shorten it up by quite a bit. I'd like to have a reasonable explanation for the client, though.
Only the computers at this one dealership have this symptom: page 1 displays fine. Page 2 returns a blank screen. Not even the obligatory <html></html> in the source that IE seems to toss in just for fun when there's nothing to display. It just dies.
I'm starting by moving some processing out of the querystring and into a text file or the database. That'll shorten it up by quite a bit. I'd like to have a reasonable explanation for the client, though.
no subject
Date: 2007-03-23 14:33 (UTC)My 2p worth...
(no subject)
From:no subject
Date: 2007-03-23 14:45 (UTC)On the browser side, IE's limit is both smaller than Firefox's and less elegantly handled. Microsoft states that the URL limit for IE is 2084 chars, but I believe that to be version specific and to have been increased in 2006 sometime with an update to IE 6. We hit it in 2005 with < 1k of URL.
You might validate the version of whatever browser they're using versus other customers who aren't having the problem. We recently hit an issue in IE where a security patch applied to IE6 in November 2006 hosed cross window javascript communication in some cases.
You might check the logs for the HTTP server though. IE doesn't supply the tags. That would lead me to believe that something is happening on the server side before the headers are prepared. It's possible that something is being added to the URL or it's being munged into a state that the server doesn't like (maybe something isn't encoded well.) We have this problem periodically with some users in regards to toolbars (Yahoo, Google, etc) and misc crap they're not supposed to have installed.
- Jeho
(no subject)
From:(no subject)
From:no subject
Date: 2007-03-23 15:29 (UTC)I face this regularly with the caliber of user we support.
Telling them they're a Knob is rarely helpful, though momentarily gratifying :)
(no subject)
From:(no subject)
From: