You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Doug Wright <do...@grabbag.on.ca> on 2002/05/05 04:06:32 UTC
2.0.35, SSI and cache
Hi all.
Hopefully the answer to this has not already been posted. I did not see any
solutions in the April archives of this list so here goes...
I've been following the discussion regarding Apache 2.0.35, server side
includes and cache. I'm having the same problem.
>From what I've discoved it seems to be a combination of 2.0.35 and HTTP 1.1
clients. If I use Mozilla 0.9.9 or IE 5 to access a cached page with a hit
counter implemented with SSI the server always responses with 304 Not Modifed.
Therefore the page is not reloaded and the counter doesn't increment.
Whereas with Netscape 4.76 (using HTTP 1.0) the client does not send any
headers pertaining to the last modified date of the file and the page is
reloaded appropriately. I used Ethereal, sniffing my eth0 interface to
gather this data.
I've played with various settings of Xbithack, FileETag and mod_expires
directives for two days with no luck.
This all started with my upgrade to 2.0.35. My last version (1.3.20) worked
fine with HTTP 1.0 or 1.1 clients.
Any thoughts?
-Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: 2.0.35, SSI and cache
Posted by Octavian Rasnita <or...@home.ro>.
Thanks, but there is no Windows binary for this alpha version.
Teddy,
orasnita@home.ro
----- Original Message -----
From: "Joshua Slive" <jo...@slive.ca>
To: <us...@httpd.apache.org>
Sent: Sunday, May 05, 2002 9:27 PM
Subject: Re: 2.0.35, SSI and cache
Octavian Rasnita wrote:
> I've discovered that using www.host.com/index.shtml make the SSI work but
> using only
> www.host.com/ doesn't work.
> ... even the same file is loaded.
Try 2.0.36 (alpha):
http://httpd.apache.org/dev/dist/
Joshua.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: 2.0.35, SSI and cache
Posted by Joshua Slive <jo...@slive.ca>.
Octavian Rasnita wrote:
> I've discovered that using www.host.com/index.shtml make the SSI work but
> using only
> www.host.com/ doesn't work.
> ... even the same file is loaded.
Try 2.0.36 (alpha):
http://httpd.apache.org/dev/dist/
Joshua.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: 2.0.35, SSI and cache
Posted by Octavian Rasnita <or...@home.ro>.
I've discovered that using www.host.com/index.shtml make the SSI work but
using only
www.host.com/ doesn't work.
... even the same file is loaded.
Teddy,
orasnita@home.ro
----- Original Message -----
From: "Doug Wright" <do...@grabbag.on.ca>
To: <us...@httpd.apache.org>
Sent: Sunday, May 05, 2002 5:06 AM
Subject: 2.0.35, SSI and cache
Hi all.
Hopefully the answer to this has not already been posted. I did not see any
solutions in the April archives of this list so here goes...
I've been following the discussion regarding Apache 2.0.35, server side
includes and cache. I'm having the same problem.
>From what I've discoved it seems to be a combination of 2.0.35 and HTTP 1.1
clients. If I use Mozilla 0.9.9 or IE 5 to access a cached page with a hit
counter implemented with SSI the server always responses with 304 Not
Modifed.
Therefore the page is not reloaded and the counter doesn't increment.
Whereas with Netscape 4.76 (using HTTP 1.0) the client does not send any
headers pertaining to the last modified date of the file and the page is
reloaded appropriately. I used Ethereal, sniffing my eth0 interface to
gather this data.
I've played with various settings of Xbithack, FileETag and mod_expires
directives for two days with no luck.
This all started with my upgrade to 2.0.35. My last version (1.3.20) worked
fine with HTTP 1.0 or 1.1 clients.
Any thoughts?
-Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: 2.0.35, SSI and cache
Posted by Doug Wright <do...@grabbag.on.ca>.
On 2002 05 04 23:43, Jay Turberville wrote:
>I'm pretty sure that this was left with "it broke with the 2.0.35 release.
>(Presumably you are referring to the Win32 version of Apache.)
>
>See the "Bug in Apache 2?" thread.
>
>Right now it looks like there is no real solution except to go back to the
>older version or suffer with the problem. I'm not aware of any workarounds
>being posted.
>
>Jay Turberville
I did see some mention of SSI issues in the bug tracking system, but I didn't
think it related to this particular problem. I'm running linux.
I did a couple of small tests and it seems if the entire document is served
from a script it works fine. So this problem must be related to SSI alone.
I guess I'll just to that for now. I bit of a drag though for a 99% static
page.
-Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: 2.0.35, SSI and cache
Posted by Jay Turberville <ja...@studio522.com>.
I'm pretty sure that this was left with "it broke with the 2.0.35 release.
(Presumably you are referring to the Win32 version of Apache.)
See the "Bug in Apache 2?" thread.
Right now it looks like there is no real solution except to go back to the
older version or suffer with the problem. I'm not aware of any workarounds
being posted.
Jay Turberville
----- Original Message -----
From: "Doug Wright" <do...@grabbag.on.ca>
To: <us...@httpd.apache.org>
Sent: Saturday, May 04, 2002 7:06 PM
Subject: 2.0.35, SSI and cache
> Hi all.
>
> Hopefully the answer to this has not already been posted. I did not see
any
> solutions in the April archives of this list so here goes...
>
> I've been following the discussion regarding Apache 2.0.35, server side
> includes and cache. I'm having the same problem.
>
> >From what I've discoved it seems to be a combination of 2.0.35 and HTTP
1.1
> clients. If I use Mozilla 0.9.9 or IE 5 to access a cached page with a
hit
> counter implemented with SSI the server always responses with 304 Not
Modifed.
> Therefore the page is not reloaded and the counter doesn't increment.
>
> Whereas with Netscape 4.76 (using HTTP 1.0) the client does not send any
> headers pertaining to the last modified date of the file and the page is
> reloaded appropriately. I used Ethereal, sniffing my eth0 interface to
> gather this data.
>
> I've played with various settings of Xbithack, FileETag and mod_expires
> directives for two days with no luck.
>
> This all started with my upgrade to 2.0.35. My last version (1.3.20)
worked
> fine with HTTP 1.0 or 1.1 clients.
>
> Any thoughts?
>
> -Doug
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: 2.0.35, SSI and cache - 2.0.36 update
Posted by Jay Turberville <ja...@studio522.com>.
I just installed 2.0.36 on my local test server and I observe that the SSI
caching appears OK now with both Netscape 6.2 and IE 5.5. I'm running
2.0.36 and the browsers on WinNT 4.0 sp6.
The following are the before and after header responses for my index page
NOT explicitely called. Note that the Content Length tag is also no longer
there and I am observing that this page is no longer being truncated
innapropriately. It is displaying fully.
HTTP/1.1 200 OK
Date: Tue, 07 May 2002 07:58:06 GMT
Server: Apache/2.0.35 (Win32)
Last-Modified: Wed, 24 Apr 2002 06:16:12 GMT
ETag: "0-154d-deb2c526"
Accept-Ranges: bytes
Content-Length: 5453
Connection: close
Content-Type: text/html; charset=ISO-8859-1
<HTML><HEAD>
HTTP/1.1 200 OK
Date: Tue, 07 May 2002 08:05:41 GMT
Server: Apache/2.0.36 (Win32)
Accept-Ranges: bytes
Connection: close
Content-Type: text/html; charset=ISO-8859-1
<HTML><HEAD>
And lastly, perl script shebang lines are now working with the traditional
declaration without the .exe suffix or with it. It is working fine either
way right now for me.
#!C:/Perl/bin/perl
or
#!C:/Perl/bin/perl.exe
Jay Turberville
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: 2.0.35, SSI and cache
Posted by reddog <re...@mored.net>.
I stand corrected. I am using <!--#echo var = "DATE_LOCAL" --> with 2.0.36
and it responds correctly when accessed with Netscape 6.
Netscape 4.78 and IE 5.5 both fail to update correctly.
Apache was compiled with "
prefix=/usr/local/apache2 --enable-ssl --enable-cgi
Sometimes the person reporting is not as well versed as he should be.
I have no clue how to do some of the things requested. I have tried to read
the response headers following some of the examples listed, but they don't
seem to work correctly. Is there any information available on this??
Rolf Olsen
----- Original Message -----
From: "Joshua Slive" <jo...@slive.ca>
To: <us...@httpd.apache.org>
Sent: Monday, May 06, 2002 12:40 PM
Subject: Re: 2.0.35, SSI and cache
>
> On Mon, 6 May 2002, reddog wrote:
>
> > Your not alone.
> > See subject "Bug in Apache2?" also.
> >
> > The bad news is, alpha 2.0.36 does not seem to fix it.
>
> If you are still getting this in 2.0.36, then it needs to be looked at
> further. Please provide:
>
> 1. The exact details on how you are configuring SSI.
>
> 2. The HTTP request and response headers for a transaction that
> is being cached but shouldn't be.
>
> Joshua.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: 2.0.35, SSI and cache
Posted by Joshua Slive <jo...@slive.ca>.
On Mon, 6 May 2002, reddog wrote:
> Your not alone.
> See subject "Bug in Apache2?" also.
>
> The bad news is, alpha 2.0.36 does not seem to fix it.
If you are still getting this in 2.0.36, then it needs to be looked at
further. Please provide:
1. The exact details on how you are configuring SSI.
2. The HTTP request and response headers for a transaction that
is being cached but shouldn't be.
Joshua.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: 2.0.35, SSI and cache
Posted by reddog <re...@mored.net>.
Your not alone.
See subject "Bug in Apache2?" also.
The bad news is, alpha 2.0.36 does not seem to fix it.
Keep the faith
Rolf Olsen
----- Original Message -----
From: "Doug Wright" <do...@grabbag.on.ca>
To: <us...@httpd.apache.org>
Sent: Saturday, May 04, 2002 10:06 PM
Subject: 2.0.35, SSI and cache
> Hi all.
>
> Hopefully the answer to this has not already been posted. I did not see
any
> solutions in the April archives of this list so here goes...
>
> I've been following the discussion regarding Apache 2.0.35, server side
> includes and cache. I'm having the same problem.
>
> >From what I've discoved it seems to be a combination of 2.0.35 and HTTP
1.1
> clients. If I use Mozilla 0.9.9 or IE 5 to access a cached page with a
hit
> counter implemented with SSI the server always responses with 304 Not
Modifed.
> Therefore the page is not reloaded and the counter doesn't increment.
>
> Whereas with Netscape 4.76 (using HTTP 1.0) the client does not send any
> headers pertaining to the last modified date of the file and the page is
> reloaded appropriately. I used Ethereal, sniffing my eth0 interface to
> gather this data.
>
> I've played with various settings of Xbithack, FileETag and mod_expires
> directives for two days with no luck.
>
> This all started with my upgrade to 2.0.35. My last version (1.3.20)
worked
> fine with HTTP 1.0 or 1.1 clients.
>
> Any thoughts?
>
> -Doug
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org