@Reporter: Please provide sample URL or test file to test this issue. This would help in further debugging of the issue.

cc'ing @mkwst from 704123 for further inputs on this.

Thanks!

I don't have time to set up a server with a test page on it with the correct headers I'm afraid. 

One additional thing to note is that this issue only occurs with the "Web Page, HTML Only" mode. If you choose "Web Page, Complete" no new request is made to the server. 

This to me says the approach of just saving the raw HTML without making an additional request would probably make the most sense and would make the 2 "Save As" modes more consistent.

Thank you for providing more feedback. Adding the requester to the cc list.

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

Tried testing the issue on mac 10.12.6 using chrome reported version #65.0.3325.146 and latest canary #67.0.3365.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Saved a webpage with the "Web Page, HTML Only" mode.
2. Opened the .htm file in chrome.
3. Observed that 0 cookies were sent when clicked on the secure button in the omnibox.

Note: Same behavior is observed in M60 also.

reporter@ - Could you please check the attached screen cast and please let us know if it is the issue you are talking about.

Thanks...!!

Deleted: 819633.mp4 3.4 MB

	819633.mp4 3.4 MB View Download

I'm not sure what cookies you were expecting to be sent in this case? To my knowledge cookies are an http only mechanism and not supported when using file:// urls. In any case before a cookie is sent, it needs to be set by something which you're not doing in this video, so there's no way any cookies would be sent in this case. I think it would be helpful for this to be investigated by someone who has experience with cookies and cache control settings.

The approximate steps to repro are as follows:

- Set up a remote web server with 2 pages:
  1 A page which sets a cookie with samesite=true
  2 A page with some server side behaviour which depends on that cookie (eg showing "cookie present" on the page if it is present) and which sets the 'Cache-Control: no-store' header
- Browse to webpage 1 and check that the cookie has been set
- Browse to webpage 2 and check that the cookie has been sent to this page (ie "cookie present" is shown)
- Right click save as Web Page, HTML Only on page 2 - "cookie present" won't be saved

Thank you for providing more feedback. Adding the requester to the cc list.

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

This issue seems to be out of ET scope, to test this issue remote web service should be established. Hence adding TE-NeedsTriageHelp label. Could someone from the Internals>Network>Cookies team have a look into this issue.

Thanks!

I will remove the SecurityFeature component as I believe this is entirely related to the interaction between cookies and savepage

Removing the cookies label - happy to discuss cookies with the SavePage folks, but the cookie code doesn't know what SavePage is, and it's up to the consumer to correctly configure the network requests they make.