adding some people who git blame says works on plznavigate if someone wants to start looking at this. I haven't yet done a repro, will update the bug when I have a confirmed repro.

 Is there a plznavigate crbug component?

hmm I can't repro this on 63.0.3227.0 is this a recent regression?

Historically, this was first reported as  Issue 454 .

This page serves the (self-contradictory) directive:

  Cache-Control: public, max-age=31536000, no-cache

...which means that Chrome caches the resource but requires revalidation before reuse. I see that revalidation happening, and the server respond with a 401, which the client respects and prompts the user for credentials.

A network log of the repro (see https://dev.chromium.org/for-testers/providing-network-details) would probably help clarify what's going on here.

Just to clarify steps:

1. Select 'Continue where you left off' option for 'On start-up' setting
2. Enable chrome://flags/#browser-side-navigation
...

Same thing happens for http://www.pagetutor.com/keeper/mystash/secretstuff.html (jimmy/page) which doesn't set any cache response headers. I can reproduce it on 62.0.3202.52.

I reported this as it looked like regression after #browser-side-navigation got enabled by default. But as mentioned in  Issue 454  it currently works like in other browsers. On Mac it works in following way:
- Safari: page loaded from cache; no authorization dialog
- Firefox: page loaded from cache; no authorization dialog
- Chrome (enabled #browser-side-navigation): page loaded from cache; no authorization dialog
- Chrome (disabled #browser-side-navigation): no page; authorization dialog shown
For some reason it was changed since  Issue 454  was closed but now it's back to same behaviour as other browser.

So if we are now behaving like other browsers, is this something we should fix?

Observations:
--------------
1. Able to reproduce this issue on Windows-10, Ubuntu 14.04 and Mac OS 10.12.6 using chrome latest stable #62.0.3202.75 and canary #64.0.3256.0 by following steps mentioned in the original comment.
2. This issue is only reproducible when chrome://flags/#browser-side-navigation is enabled, issue is not seen if this flag is disabled
3. After step-4 observed the login dialog box is displayed after refreshing the page with the content in the background.

Could anyone let us know is there any latest update available on this issue?

Thanks!

Network bug triager here.  Friendly ping, can anyone comment if this issue still valid?

I'm closing this for lack of activity. Please file a new bug if you can provide the information requested.