I know this thread is rather lengthy, and took a few turns along the way,
but I ran across this link the other day and thought it might be of use for
everyone on the list - it's an official explanation of how IE handlers
caching via headers. there's also a few links in it that are worth noting
In your Apache::ASP version, try setting Expires to tell IE
to cache explicitly...
$Response-{Expires} = 86400; # cache until tomorrow
--Joshua
_
Joshua Chamas Chamas Enterprises Inc.
NodeWorks free
| In your Apache::ASP version, try setting Expires to tell IE
| to cache explicitly...
| $Response-{Expires} = 86400; # cache until tomorrow
I did that. And and also tried
$r-add_header('Expires',HTTP::Date::time2str(time+86400)); in a normal .pl
file. In fact, the first header dump in my
I saw your header, but couldn't tell that it was for tomorrow,
with the GMT time zone info. I don't read GMT go figure ;)
What I would recommend is trying to match the headers exactly
as when serving up the static file since we know that works,
oh and make sure the file extension is the same
| I saw your header, but couldn't tell that it was for tomorrow,
| with the GMT time zone info. I don't read GMT go figure ;)
Euhmmm... If I'm not mistaken, 19 october actually is next *month*, even in
your timezone ;)
| ... maybe IE is "smart" enough to see the .pl in the path and guess
|
Hi there,
On Tue, 19 Sep 2000, Ime Smits wrote:
Does anybody know of a tool to get a complete log on every piece of
information communicated between browser and server?
'sfunny, I asked Josh the same question a couple of weeks ago...
I think it's called a packet sniffer. I've had some
* G.W. Haywood ([EMAIL PROTECTED]) [000919 06:54]:
Hi there,
On Tue, 19 Sep 2000, Ime Smits wrote:
Does anybody know of a tool to get a complete log on every piece of
information communicated between browser and server?
'sfunny, I asked Josh the same question a couple of weeks ago...
OK, did it the hardway: after a lot of tcpdump -i -s 500, grepping and
stringing, I tackled it. Halfway.
IMHO, it boils down to both a IE bug and a somehow 'hidden' feature of
Apache. It seems that on script execution an extra header "Vary: Host" is
sent to the browser.
This is what the RFC's
Ime Smits wrote:
Below is a sample of the headers it returns. Any ideas? Anything that is
communicated without me seeing it?
8 Content-Length: 294
and here for the same image, but as a normal static file fron disk:
8 Content-Length: 327
How come that the sizes are different?
| 8 Content-Length: 294
| 8 Content-Length: 327
| How come that the sizes are different?
The images are dynamically generated png's with GD, but however the contents
may change every time you view a page, it's not necessary for the browser to
constantly get a fresh copy when doing a javascript
10 matches
Mail list logo