Currently, the Chrome browser plugin uses the webRequest Chrome API to detect all HTTP requests (including non-AJAX requests), but it doesn't actually capture the HTTP response headers for them. This means the plugin can't actually capture the server-generated provenance URL, which is specified as an HTTP header.
It turns out that HTTP headers can be captured after all, just by adding ["responseHeaders"] as an extra argument 😄 Some quick testing in Windows shows this works.
Currently, the Chrome browser plugin uses the
webRequestChrome API to detect all HTTP requests (including non-AJAX requests), but it doesn't actually capture the HTTP response headers for them. This means the plugin can't actually capture the server-generated provenance URL, which is specified as an HTTP header.It turns out that HTTP headers can be captured after all, just by adding
["responseHeaders"]as an extra argument 😄 Some quick testing in Windows shows this works.