Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Date: Thu, 17 Dec 2009 15:46:43 +0100
From: "Abid Hussain" <abid.hussain@dilax.com>
To: users <users@tomcat.apache.org>
Message-ID: <H00000db0054c33c.1261061203.postamt.berlin.dilax.com@MHS>
In-Reply-To: <948126CDFED9634D8B12AF27F009EDC501D95C7A@oce-exbe03-v.oce.net>
Subject: AW: RE: RE: Ignore http header if-modified-since
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

this is interesting. As you see in my example (i put it again below),=20
tomcat itself delivers the Last-Modified (Do, 17 Dez 2009 11:11:29 GMT)=20
in a different locale (german) as the Date Header (Thu, 17 Dec 2009=20
11:24:53 GMT).

So maybe the simplest way is to prevent tomcat from putting the=20
"Last-Modified" Header into the response. Do I have to use a Filter to=20
do so or can this be done by another way (by configuration, ...)?

Best regards,

Abid

--> Successful Request:
Host: localhost:8080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.6)
Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729)
Accept: text/html,application/xhtml+xml,application/xml;q=3D0.9,*/*;q=3D0=
=2E8
Accept-Language: de-de,en-us;q=3D0.8,de;q=3D0.6,en;q=3D0.4,fr-fr;q=3D0.2
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=3D0.7,*;q=3D0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: JSESSIONID=3D262FAFFC220AF50656BC67C1C1DD1331
Cache-Control: max-age=3D0
--> Response:
Server: Apache-Coyote/1.1
Last-Modified: Do, 17 Dez 2009 11:11:29 GMT
Content-Type: text/javascript
Transfer-Encoding: chunked
Date: Thu, 17 Dec 2009 11:24:53 GMT

-----Urspr=FCngliche Nachricht-----
Von: Looijmans, Mike [mailto:mike.looijmans@oce.com]=20
Gesendet: Donnerstag, 17. Dezember 2009 15:03
An: Tomcat Users List
Betreff: RE: RE: Ignore http header if-modified-since

This header is invalid:

Last-Modified: Do, 17 Dez 2009 11:11:29 GMT=20

This is not according to spec, "Dez" should be "Dec". Maybe tomcat=20
chokes on it.


> -----Original Message-----
> From: Abid Hussain [mailto:abid.hussain@dilax.com]
> Sent: donderdag 17 december 2009 12:26
> To: users
> Subject: AW: RE: Ignore http header if-modified-since
>=20
> Hallo,
>=20
> unfortunately it is a 404. And the 404 is only delivered when the=20
> request header contains "if-modified-since". If not the request is=20
> respondec correctly. This behaviour is reproducable.
>=20
> Below you find an example of failed and successful request.=20
> The GET URL is in both cases
> http://localhost:8080/mywebapp/faces/static/META-INF/progressb
ar/script.js
>=20
> --> Failed Request (means tomcat responds with 404):
> Host: localhost:8080
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.6)
> Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729)
> Accept:=20
> text/html,application/xhtml+xml,application/xml;q=3D0.9,*/*;q=3D0.8
> Accept-Language: de-de,en-us;q=3D0.8,de;q=3D0.6,en;q=3D0.4,fr-fr;q=3D0.=
2
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=3D0.7,*;q=3D0.7
> Keep-Alive: 300
> Connection: keep-alive
> Cookie: JSESSIONID=3D262FAFFC220AF50656BC67C1C1DD1331
> If-Modified-Since: Do, 17 Dez 2009 11:11:29 GMT
> Cache-Control: max-age=3D0
> --> Response:
> Server: Apache-Coyote/1.1
> Content-Type: text/html
> Content-Length: 1093
> Date: Thu, 17 Dec 2009 11:24:38 GMT
>=20
> --> Successful:
> Host: localhost:8080
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.6)
> Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729)
> Accept:=20
> text/html,application/xhtml+xml,application/xml;q=3D0.9,*/*;q=3D0.8
> Accept-Language: de-de,en-us;q=3D0.8,de;q=3D0.6,en;q=3D0.4,fr-fr;q=3D0.=
2
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=3D0.7,*;q=3D0.7
> Keep-Alive: 300
> Connection: keep-alive
> Cookie: JSESSIONID=3D262FAFFC220AF50656BC67C1C1DD1331
> Cache-Control: max-age=3D0
> --> Response:
> Server: Apache-Coyote/1.1
> Last-Modified: Do, 17 Dez 2009 11:11:29 GMT
> Content-Type: text/javascript
> Transfer-Encoding: chunked
> Date: Thu, 17 Dec 2009 11:24:53 GMT
>=20
> Does anybody have an explanation for this?
>=20
> Best regards,
>=20
> Abid
>=20
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: Looijmans, Mike [mailto:mike.looijmans@oce.com]
> Gesendet: Mittwoch, 16. Dezember 2009 15:48
> An: Tomcat Users List
> Betreff: RE: Ignore http header if-modified-since
>=20
> I assume you mean 304 (Not modified) instead of 404 (Not found).
>=20
> Simplest I can think of is to NOT put the "last-modified"=20
> header in your response. Then the browser won't send you an=20
> if-modified-since back.
>=20
> On the other hand, if you can put a datestamp on the response
> - e.g. a file date or by reading it from a DB or so - provide the=20
> proper response and you get client-side caching for
> (almost) free, which can seriously reduce load on a server.
>=20
> M.
>=20
> > -----Original Message-----
> > From: Abid Hussain [mailto:abid.hussain@dilax.com]
> > Sent: woensdag 16 december 2009 14:11
> > To: users
> > Subject: Ignore http header if-modified-since
> >=20
> > Hallo,
> > =20
> > when processing ajax-requests Tomcat sometimes responds with a 404=20
> > instead of delivering XML.
> > =20
> > This seems to happen when the http header "if-modified-since"=20
> > in the request doesn't somehow contain "the right" value.=20
> At least, if
>=20
> > the request doesn't contain this header, tomcat responds
> "correctly".
> >=20
> > Is it possible to instruct tomcat to simply ignore this
> header so that
>=20
> > the correct response will be delivered, whatever is
> contained in this
> > header?
> >=20
> > Best regards,
> >=20
> > Abid
>=20
> (EOF)
>=20
> This message and attachment(s) are intended solely for use by the=20
> addressee and may contain information that is privileged, confidential=20

> or otherwise exempt from disclosure under applicable law.
>=20
> If you are not the intended recipient or agent thereof responsible for=20

> delivering this message to the intended recipient, you are hereby=20
> notified that any dissemination, distribution or copying of this=20
> communication is strictly prohibited.
>=20
> If you have received this communication in error, please notify the=20
> sender immediately by telephone and with a 'reply' message.
>=20
> Thank you for your co-operation.
>=20
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>=20
>=20
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>=20
>=20
>=20

This message and attachment(s) are intended solely for use by the=20
addressee and may contain information that is privileged, confidential=20
or otherwise exempt from disclosure under applicable law.

If you are not the intended recipient or agent thereof responsible for=20
delivering this message to the intended recipient, you are hereby=20
notified that any dissemination, distribution or copying of this=20
communication is strictly prohibited.

If you have received this communication in error, please notify the=20
sender immediately by telephone and with a 'reply' message.

Thank you for your co-operation.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org