webRequest header access changes in Chrome 72 #264
Closed
Comments
|
@clarkduvall thanks for the heads up. It looks like Chrome 72 is due out on Jan 29th so we'll need to get this resolved before then. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like Ghostery is accessing or modifying headers that will not be available by default in Chrome 72 (currently on the dev channel). These include:
Request headers:
Response headers:
To access these headers you will need to add 'extraHeaders' in the extraInfoSpec of the relevant webRequest listeners.
See the post on the chromium-extensions Google Group for more info: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-extensions/vYIaeezZwfQ
The text was updated successfully, but these errors were encountered: