https://bz.apache.org/bugzilla/show_bug.cgi?id=65281
--- Comment #5 from Konstantin Kolinko <knst.koli...@gmail.com> ---
(In reply to François PLOU from comment #0)
> 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
As you can see above, there are the following headers:
> Last-Modified: Thu, 01 Apr 2021 15:36:29 GMT
> Expires: ven., 30 avr. 2021 13:47:45 +0200
In attachment 37842 (from comment #2), the broken (400) response contains:
> "headers": [
> {
> "name": "Last-Modified",
> "value": "jeu., 1 avr. 2021 17:37:40 +0200"
> },
>...
> {
> "name": "Expires",
> "value": "ven., 14 mai 2021 14:36:45 +0200"
> },
Please note, that the values above that are not in English are illegal for
those headers.
RFC 7232 ch.2.2 defines
> Last-Modified = HTTP-date
RFC 7234 ch.5.3 defines
> Expires = HTTP-date
RFC 7231 ch.7.1.1.1 defines
> HTTP-date = IMF-fixdate / obs-date
and IMF-fixdate is defined in English (with fixed character strings for "Mon"
etc.)
> IMF-fixdate = day-name "," SP date1 SP time-of-day SP GMT
> ; fixed length/zone/capitalization subset of the format
> ; see Section 3.3 of [RFC5322]
>
> day-name = %x4D.6F.6E ; "Mon", case-sensitive
> / %x54.75.65 ; "Tue", case-sensitive
> / %x57.65.64 ; "Wed", case-sensitive
> / %x54.68.75 ; "Thu", case-sensitive
> / %x46.72.69 ; "Fri", case-sensitive
> / %x53.61.74 ; "Sat", case-sensitive
> / %x53.75.6E ; "Sun", case-sensitive
https://cwiki.apache.org/confluence/display/TOMCAT/Specifications
As other response (with status 200) from the same har file has a correct
header, I guess that this response is not generated by Apache Tomcat.
1. I suggest you to find out, what generates that incorrect response.
2. Regarding you problem:
- Please verify, whether the request has reached Apache Tomcat. (E.g. enable an
access log).
- If the proxy sends incorrect headers to Tomcat, Tomcat can respond with error
400.
BTW,
> X-Cache: MISS from kamino
> X-Cache-Lookup: MISS from kamino:3128
> Via: 1.0 kamino (squid/3.1.23)
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
