-
Notifications
You must be signed in to change notification settings - Fork 9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser caching doesn't seem to work #487
Comments
Ouch, you are likely getting into the wrong branch of this. The way it works is that browser receives 304, but instead of passing it into Blink, it is fetching data from disk cache and feeds Blink with the 200 response. Clueless renderer behaves as it is getting an OK response. Not getting into that branch means that we don't have raw headers, don't report precise network timing, etc. I.e. needs to be fixed on the headless side. If you see this on Linux/Window headless and don't see it on a Mac, we are not plumbing the raw headers information the right way. Should be a straightforward fix in |
@pavelfeldman doesn't seem to be related to headless: it reproduces for me on mac headful and on mac headless. |
Pavel bisected it down to chromium change. |
For the record: this was fixed upstream in r498894. |
The new chromium: - supports executionContextId in Runtime.callFunctionOn protocol method - supports passing objects as arguments in Runtime.callFuntionOn protocol method This roll also fixes puppeteer#487.
The new chromium: - supports executionContextId in Runtime.callFunctionOn protocol method - supports passing objects as arguments in Runtime.callFuntionOn protocol method This roll also fixes #487.
Still not getting the cache, all resources(png, css) got 200, but I'm using headless mode. Tested in v1.0.0-rc:
|
@pokka the same happens to me if I just open the website in chrome and try to reload: all resources are loaded with 200 (check out devtools network panel). Looks like server disabled caching. |
Any update on this? :) |
@robba86 this has been fixed; if it doesn't work for you - please file another issue. |
@pokka it's working for me set then search for |
The following example reloads the
example.com
a few times.For some reason, all the responses have status 200. If there was a caching, the responses would have status 304.
This was initially reported in #446.
The text was updated successfully, but these errors were encountered: