httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jennifer R. Lee" <>
Subject [users@httpd] RE: [SPAM] - Re: [users@httpd] why do I get a 304 when I replace a file with a changed version? - Email found in subject
Date Thu, 04 May 2006 22:18:49 GMT
Thanks! I should of noted that touch works as well, so I suspect if that is what 'more' does
it would work to. I'll try it(I have to wait for ttl to expire so it takes awhile), and will
post only if it does not work. I just think it's odd that we would have to use these more
unusual methods to copy the files to get the server to recognize a change. When I use copy,
xcopy, etc. the time stamps do change, eg. a.htm picks up the time stamp of b.htm so it is
different as is the file size. 
We can doc to only use cp or touch(after a copy), but I am sure at some point someone will
forget and therefor their new doc will never be posted until they check and correct the method
they used to replace the file. That's what I plan to do for now anyway.
Thanks again!
Jennifer Lee


From: William A. Rowe, Jr. []
Sent: Thu 5/4/2006 5:27 PM
Subject: [SPAM] - Re: [users@httpd] why do I get a 304 when I replace a file with a changed
version? - Email found in subject

Jennifer R. Lee wrote:
> If I use windows xcopy command, copy command, drag and drop or even the unix
> toolkit mv command to swap these two files and then launch a.htm, Apache acts
> as if there was no change, and sends a 304 every time the TTL expires

Just a wild observation, but xcopy/copy/etc all preserve the time stamp on win.

If you use

more a.htm > b.htm

what happens?  This will 'touch' the datestamp of b.htm to the current time.

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message