Bug 143020 – [WK2] Responses with 204 HTTP Status Code should be cacheable by default

• Component: WebKit2
• Status: RESOLVED FIXED

[Chris Dumez]

Responses with 204 HTTP Status Code should be cacheable by default according to RFC 7231:
"""
   A 204 response is cacheable by default; i.e., unless otherwise
   indicated by the method definition or explicit cache controls (see
   Section 4.2.2 of [RFC7234]).
""" [1]

[1] http://tools.ietf.org/html/rfc7231#section-6.3.5

The new WebKit Network cache does not currently cache these, even if Cache-Control headers allow us to do so.

[Radar WebKit Bug Importer]

<rdar://problem/20281529>

[Chris Dumez]

Created attachment 249355 [details]
Patch

[Antti Koivisto]

Comment on attachment 249355 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=249355&action=review

> LayoutTests/http/tests/cache/disk-cache/resources/cache-test.js:46
> -    var testURL = "resources/generate-response.cgi?uniqueId=" + uniqueTestId++ + "&Content-type=text/plain";
> +    var cgi_script = withBody ? "resources/generate-response.cgi" : "resources/generate-response-no-body.cgi";
> +    var testURL = cgi_script + "?uniqueId=" + uniqueTestId++ + "&Content-type=text/plain";

Maybe body generation should just be an argument for the script? Otherwise we need to keep these in sync if we add features.

[Chris Dumez]

Created attachment 249361 [details]
Patch

[Chris Dumez]

Comment on attachment 249361 [details]
Patch

Clearing flags on attachment: 249361

Committed r181920: <http://trac.webkit.org/changeset/181920>

[Chris Dumez]

All reviewed patches have been landed.  Closing bug.