b.com/golang/go/pull/42597
[3] https://github.com/golang/net/pull/96
[4] https://github.com/golang/go/issues/18594
[5] https://github.com/golang/go/issues/51361
Mitar
Mitar
--
http://mitar.tnode.com/
https://twitter.com/mitar_m
--
You received this message because you are subscribed to the Googl
limitation of Early Hints seems to be that resources which require
Authorization header cannot be preloaded, am I mistaken? With HTTP2 push
you can push such a resource and add a corresponding anticipated header.
Mitar
On Wed, Mar 16, 2022 at 7:05 AM Kenji Baheux
wrote:
> Hi Thomas,
>
>
ts. While HTTP2 push can support such use
cases.
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=962642
Am I missing something obvious about the Link header which would address
those concerns?
Mitar
--
http://mitar.tnode.com/
https://twitter.com/mitar_m
--
You received this messag
s not
support all use cases.
Currently to me it looks like the best bet is to move the bearer token
to Cookie header. That one might be included when doing a preload
through Link header.
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=962642
[2] https://bugs.chromium.org/p/chromium/issues/d
what is used as an Accept header with link
rel="preload" and as="fetch" and it looks like Chrome always sets
Accept: */*, even if you specify type="application/json".
Mitar
On Sun, Jul 10, 2022 at 8:04 PM Mitar wrote:
>
> Hi!
>
> On Sun, Jul
Hi!
Done: https://bugs.chromium.org/p/chromium/issues/detail?id=1415291
Mitar
On Wed, Nov 2, 2022 at 11:46 PM Mike Taylor wrote:
>
> Hi Mitar,
>
> This is really good feedback. Would you mind filing a bug at
> crbug.com/new? Feel free to respond here with the link.
>
