For the techies in my life...
Mar. 23rd, 2007 09:18![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
mapsedgeSo, 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.