https://bz.apache.org/bugzilla/show_bug.cgi?id=65281
Bug ID: 65281
Summary: Tomcat does not process correctly Etag and send HTTP
400 error code
Product: Tomcat 9
Version: 9.0.45
Hardware: PC
OS: Linux
Status: NEW
Severity: regression
Priority: P2
Component: Connectors
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: -----
When a response to a request contains following header (and more specially the
Etag attribute) :
Cache-Control, Etag, Expires, Last-Modified as this example :
HTTP/1.1 200 OK
Last-Modified: Thu, 01 Apr 2021 15:36:29 GMT
Cache-Control: public, must-revalidate
Expires: ven., 30 avr. 2021 13:47:45 +0200
Accept-Ranges: bytes
ETag: W/"12581-1617291389000"
Content-Type: text/css
Content-Length: 12581
Date: Fri, 30 Apr 2021 11:37:45 GMT
X-Cache: MISS from kamino
X-Cache-Lookup: MISS from kamino:3128
Via: 1.0 kamino (squid/3.1.23)
Connection: keep-alive
The next request of the browser on same resource will send back following
header to check if the resource has been modified :
If-Modified-Since: Thu, 01 Apr 2021 15:36:29 GMT
If-None-Match: W/"12581-1617291389000"
Normally tomcat must answer http 200 or http 304 but it sends and http 400
status.
The problems also concerns Tomcat 8.5.63.
The release 9.0.37 does not have this behaviour.
In addition, if the browser sends If-None-Match: *, the http 400 does not
occurs.
Regards
François
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
