Perlbal - MSIE's take on If-Modified-Since

This is Interesting: Free IT Magazines  
Home > Archive > Perlbal > December 2005 > MSIE's take on If-Modified-Since





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author MSIE's take on If-Modified-Since
Adam Fritzler

2005-12-31, 8:45 pm

IE supplies a length parameter to the If-Modified-Since header, causing
perlbal to incorrectly return the full content. Like so:

If-Modified-Since: Fri, 30 Dec 2005 19:03:59 GMT; length=1406

Perlbal compares the header value directly against a date string and
great waves of excessive transfer ensue.

asf.


Brad Fitzpatrick

2005-12-31, 8:45 pm

Whoa, crazy. I didn't know you could do that?

Do you want me to fix it, or did you already?


On Sat, 31 Dec 2005, Adam Fritzler wrote:

> IE supplies a length parameter to the If-Modified-Since header, causing
> perlbal to incorrectly return the full content. Like so:
>
> If-Modified-Since: Fri, 30 Dec 2005 19:03:59 GMT; length=1406
>
> Perlbal compares the header value directly against a date string and
> great waves of excessive transfer ensue.
>
> asf.
>
>


Adam Fritzler

2005-12-31, 8:45 pm

On Sat, Dec 31, 2005 at 11:59:35PM +0000, Brad Fitzpatrick wrote:

> Whoa, crazy. I didn't know you could do that?


I don't think you can. In fact, HTTP 1.1 specifies no parameters in
that header. But they do it anyway.

> Do you want me to fix it, or did you already?


My quick fix was to s/// the ; and everything after it. You can
probably make that change faster than I can make a patch.

Might want to actually check the size, but I'm not sure it's worth the
effort.

asf.


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com