Yes, I was thinking of proxyFetch as an API that wraps over a call to a
proxy, such that you could pass and get Headers objects that correspond
directly to the "raw" headers of the proxied request and response. The
proxyFetch function would then encode and decode those "raw" headers
somehow in
On Thu, Feb 23, 2023 at 10:14 AM Andreu Botella wrote:
> Sorry for taking so long to reply.
>
> One possible client-side use case enabled by this addition is as part of a
> JS API for a proxy, possibly one that allows access to public servers that
> aren't CORS-accessible:
>
> // example.com does
Sorry for taking so long to reply.
One possible client-side use case enabled by this addition is as part of
a JS API for a proxy, possibly one that allows access to public servers
that aren't CORS-accessible:
// example.com doesn't support CORS!
const {headers, body} = proxyFetch("https://exa
On Fri, Feb 10, 2023 at 7:05 PM Andreu Botella wrote:
> Contact emails abote...@igalia.com, ri...@chromium.org
>
> Explainer None
>
An explainer (or even an inline explanation of how developers are supposed
to use this) would've been helpful here. As is, I don't understand what the
implications
LGTM1
On Fri, Feb 10, 2023 at 7:05 PM Andreu Botella wrote:
> Contact emails abote...@igalia.com, ri...@chromium.org
>
> Explainer None
>
> Specification https://fetch.spec.whatwg.org/#dom-headers-getsetcookie
>
> Design docs
> https://github.com/whatwg/fetch/issues/973#issuecomment-902578584
>
Contact emails
abote...@igalia.com, ri...@chromium.org
Explainer
None
Specification
https://fetch.spec.whatwg.org/#dom-headers-getsetcookie
Design docs
https://github.com/whatwg/fetch/issues/973#issuecomment-902578584
https://github.com/whatwg/fetch/issues/9
