Anne van Kesteren

Results 403 issues of Anne van Kesteren

We want to introduce `fromCache` member on `Response` objects. However, this in part depends on how we tackle #38 and also #39 of course. If a `Response` is partially formed...

addition/proposal
needs implementer interest
topic: api

See discussion in https://github.com/WICG/cors-rfc1918/issues/24. (Maybe wait until #1118 is fixed before fixing this.)

As discussed in a long (collapsed) thread at https://github.com/whatwg/fetch/pull/1325#discussion_r729287918 it might be better to align the specification with implementations and acknowledge that internal redirects are a thing and that HSTS...

security/privacy
topic: redirects

At various times it's suggested that `Sec-*` or other new headers should be able to bypass the CORS preflight requirement. The problem with this is that servers have limits on...

In https://github.com/whatwg/fetch/issues/447#issuecomment-281731850 @jakearchibald sketched some APIs based on @stuartpb's work which @bakulf then implemented: * https://developer.mozilla.org/en-US/docs/Web/API/FetchObserver * https://dxr.mozilla.org/mozilla-central/source/dom/webidl/FetchObserver.webidl * https://dxr.mozilla.org/mozilla-central/source/dom/webidl/Request.webidl#59 That issue got closed after we landed a subset of...

addition/proposal
needs tests
topic: api
needs concrete proposal

To support something like https://w3c.github.io/server-timing/#server-timing-header-parsing-algorithm the response concept needs trailer support. I'm not sure if we need to add conceptual request trailer support as part of solving this issue as...

topic: http

These APIs had the wrong design and are also incorrectly used at times (#559). "Extract a MIME type" also needs a new design, likely on top of this as a...

topic: http

I played around a bit with WPT's H2 support and I found that Chrome is quite restrictive on header values, unless I'm missing something. Basically, if they contain (after stripping...

topic: http

We put "fetch params" in the Infrastructure section temporarily, but I think it all needs to move to the Fetching section. I think it should first have a "Fetching miscellaneous"...

clarification

@MattMenke2 made me think of another "bypass", though it would only affect naïve parsers: * `text/plain;,application/json` * `text/plain;charset=utf-8,application/json` These would only be successful with a server that splits on `,`...

security/privacy
topic: cors