Navigation tester

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.webNavigation.* and chrome.webRequest.* events to do so.

We used this when implementing a chrome.webRequest.onBeforeHeadersReceived listener 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 Content-Disposition response header handling, see https://crbug.com/696967.

Set response details:

Description	Value
Status Code:
`Content-Type` header:
`Location` header:
`Content-Disposition` header:

Notes:

Nginx sometimes messes with the Content-Type and Location headers by removing duplicate and blank values. I recommend testing the response with curl before making assumptions.
Content-Disposition can be specificed multiple times by manually adding more GET parameters.