[whatwg/fetch] Fetch should handle 'X-Frame-Options' (#302)

Probably around the same place as the other response checks at the bottom of the main fetch algorithm, though browser behavior diverges a bit with regard to whether or not a navigation actually takes place, whether an error page is rendered, etc.

There's also some strangeness around the `content-disposition` header that bit us when we moved XFO up out of blink into Chrome's browser process: see https://crbug.com/610284 That header doesn't show up in Fetch either, though I'm not really sure it ought to?

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/302