content policy filter does not handle relative Locations
This is a spinoff from #21627 (moved).
If you visit a page that returns a Location header whose value is a relative URL, the following appears on the browser console: NS_ERROR_MALFORMED_URI: Component returned failure code: 0x804b000a (NS_ERROR_MALFORMED_URI) [nsIIOService.newURI] content-policy.js:157
An URL that demonstrates the problem is http://httpstat.us/no-such-page