This test page is for testing edge-cases with browser navigations. Set the desired response
headers + status code, and then observe how the browser handles it. You can use a browser
extension that listens for the
chrome.webRequest.* events to
We used this when implementing a
in Adblock Plus that checked the response would result in a committed navigation
before handling it. That was necessary, since the
chrome.webNavigation.onCommitted event fired
too late for our purposes. During this work, we also found a bug in Chromium with
response header handling, see https://crbug.com/696967.
Set response details:
Nginx sometimes messes with the
Location headers by removing duplicate and blank
values. I recommend testing the response with curl before making
Content-Disposition can be specificed multiple times
by manually adding more GET parameters.