"CAUTION: provisional headers are shown" in Chrome debugger
I believe it happens when the actual request is not sent. Usually happens when you are loading a cached resource.
The resource could be being blocked by an extension (AdBlock in my case).
The message is there because the request to retrieve that resource was never made, so the headers being shown are not the real thing. As explained in the issue you referenced, the real headers are updated when the server responds, but there is no response if the request was blocked.
The way I found about the extension that was blocking my resource was through the net-internals tool in Chrome:
For Latest Versions of chrome
- Type
chrome://net-export/in the address bar and hit enter. - Start Recording. And save Recording file to local.
- Open the page that is showing problems.
- Go back to net-internals
- You can view Recorded Log file Here https://netlog-viewer.appspot.com/#import
- click on events (###) and use the textfield to find the event related to your resource (use parts of the URL).
- Finally, click on the event and see if the info shown tells you something.
For Older Versions of chrome
- Type
chrome://net-internalsin the address bar and hit enter. - Open the page that is showing problems.
- Go back to net-internals, click on events (###) and use the textfield to find the event related to your resource (use parts of the URL).
- Finally, click on the event and see if the info shown tells you something.
For chrome v72+ what solved it for me was only this:
go to chrome://flags/ and disable this 3 flags
- Disable site isolation
- Enable network service
- Runs network service in-process
or you can do it from command line :
chrome --disable-site-isolation-trials --disable-features=NetworkService,NetworkServiceInProcess
why this happen?
It seems that Google is refactoring their Chromium engine into modular structure, where different services will be separated into stand-alone modules and processes. They call this process servicification. Network service is the first step, Ui service, Identity service and Device service are coming up. Google provides the official information at the Chromium project site.
is it dangerous to change that?
An example is networking: once we have a network service we can choose to run it out of process for better stability/security, or in-process if we're resource constrained. source