New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 16 users
Status: Duplicate
Merged: issue 158957
Owner: ----
Closed: Nov 2012
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Sign in to add a comment
PDF can't be saved with CTRL+S or save button
Reported by, Oct 9 2012 Back to list
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.92 Safari/537.4

Steps to reproduce the problem:
1. draw an javascript link, loading <page>/<fake folder>/
2. draw a form loading a pdf wich URL is the same as in 1.
3. try to save the PDF (ctrl s) or use the button on the bottom right

The problem is that chrome take the directive "Cache-Control: no-cache, no-store, max-age=0, must-revalidate" as  if it was an interdiction to save, but no-store doesn't mean that.

14.9.2 What May be Stored by Caches

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. 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.
Even when this directive is associated with a response, users might explicitly store such a response outside of the caching system (e.g., with a "Save As" dialog). History buffers MAY store such responses as part of their normal operation.
The purpose of this directive is to meet the stated requirements of certain users and service authors who are concerned about accidental releases of information via unanticipated accesses to cache data structures. While the use of this directive might improve privacy in some cases, we caution that it is NOT in any way a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches might not recognize or obey this directive, and communications networks might be vulnerable to eavesdropping.

What is the expected behavior?
Ask where to save the PDF
Save the PDF as a file

What went wrong?
When you get a pdf from a POST query and there is a directive no-store you can't make CTRL+S or hit the save button to save the PDF.

Example URL:

Does it occur on multiple sites: Yes

Is it a problem playing media? No

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? N/A 

Chrome version: 22.0.1229.92  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Comment 1 by, Nov 3 2012
This looks like the culprit for my inability to save web banking PDF statements to disk, which forces me to switch over to Firefox once a month. Quite a nuisance - never had this problem with another browser.

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4
I constantly run into this issue when browsing journals (e.g. ScienceDirect). Extremely annoying. Chrome/23.0.1271.64
Comment 3 Deleted
Comment 4 by, Nov 26 2012
Labels: -Area-Webkit -Via-Wizard -OS-Windows Area-Internals Feature-PDF OS-All Internals-Network-Cache
Many thanks for the detailed reproduction steps, kisscool2a. I agree that this may be very annoying in some use cases, such as browsing journals.

Do you think there is a way for this to be easily fixed?
Comment 5 by, Nov 26 2012
Labels: Mstone-25
Status: Assigned
rvargas: could you take a look at this bug? Does our handling of
the "Cache-Control: no-store" directive really interfere with the
"Save as" command?

cbentzel: Do you know who works on "Save as"? It is the Download team?
Mergedinto: 145070
Status: Duplicate
#5: I actually did some of the work on Save As earlier this year (including for the PDF plugin), trying to get it 

I think there is an issue with this for POST requests. 

#5: It looks like a regression got introduced where the post id for the save as does not match the one in cache, so it is not served out of cache. I added a net-internals log for this. I can take a quick look at this particular case as well.
Attached is a net-internals file from 25.0.1335.0

Note that the post id matches on the second request (via the Save/Disk Icon in the PDF plugin), so this should not be a case of post id mismatch as I expected.
net-internals-log (9).json
135 KB View Download
Status: Assigned
And it looks like there is an ENTRY_DOOM on the posted data.

Let's keep it on rvargas.

I'll also try to reverse the duplicate issue, as this has better reproduction steps. Thanks for the clear repro case.
 Issue 145070  has been merged into this issue.
Labels: -Internals-Network-Cache Feature-Downloads
Owner: ----
Status: Untriaged
the response has
Cache-Control: no-cache, no-store

so it cannot be cached.
Status: WontFix
Labels: -Mstone-25
Status: Untriaged
Actually, moving back to Untriaged.

We won't change how no-store works with the http cache. Arguably we should change how the PDF plugin saves documents so it does not rely on the content being in the browser's http cache.
Given c#13, I'm inclined to consider this a duplicate of issue 158957.  Chris, WDYT?

Mergedinto: 158957
Status: Duplicate
Project Member Comment 16 by, Mar 10 2013
Labels: -Area-Internals -Feature-PDF -Feature-Downloads Cr-Content-Plugins-PDF Cr-Internals Cr-UI-Browser-Downloads
Project Member Comment 17 by, Apr 5 2013
Labels: Cr-Blink
Project Member Comment 18 by, Apr 6 2013
Labels: -Cr-Content-Plugins-PDF Cr-Internals-Plugins-PDF
Comment 19 by Deleted ...@, Aug 16 2013
this problem exists as at version 28.0.1500.95
still not working chrome 39 :'(
Sign in to add a comment