New issue
Advanced search Search tips

Issue 788252 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Nov 28
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Cache-Control unexpected behaviour

Reported by valerio....@gmail.com, Nov 24 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Example URL:
https://tesei.me/google/form.php

Steps to reproduce the problem:
1. Set server to response with header 'Cache-Control: no-store'
2. post data to a page
3. Right-click "view source"
4. Hit Reload as per message
5. Data is not sent back as POST, GET request is received by the server instead

What is the expected behavior?
I would expect "Resubmit Form Request" as I'm "Resubmitting" a set of data previously.
More specifically cache policy is used by the RESPONSE, so RESPONSE should NOT be cached but REQUEST should not be affected, IMHO Cache-Control should NOT be taken in consideration at ALL from the Browser, in the mater of "Resubmitting" previously submitted data.

What went wrong?
header "Cache-Control: no-store" : 
	Google Chrome does not prompt for "Resubmit Form Request", 
	shown source is GET, not POST
header "Cache-Control: no-cache" : 
	Google Chrome does not prompt for "Resubmit Form Request", 
	shows the right source.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes Version 58.0.3029.81 (64-bit)

Does this work in other browsers? Yes

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 27.0 r0
 
https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.2

The purpose of the no-store directive is to prevent the inadvertent release or retention of sensitive information (for example, on backup tapes). The no-store directive applies to the entire message, and MAY be sent either in a response or in a request. 

If sent in a request, a cache MUST NOT store any part of either this request or any response to it.
ED: It is not the case, browser does not set this Header

If sent in a response, a cache MUST NOT store any part of either this response or the request that elicited it. This directive applies to both non- shared and shared caches. "MUST NOT store" in this context means that the cache MUST NOT intentionally store the information in non-volatile storage,and MUST make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.

ED: But we aren't caching the REQUEST nor RESPONSE we are RESUBMITTING like it was the first time.
Components: -Blink Internals>Network>Cache
Hmm, can't seem to reproduce with M63/Beta; can't point to a particular change that would have fixed it, though (but I wouldn't be aware of all of them).


Project Member

Comment 4 by sheriffbot@chromium.org, Nov 28

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment