Answer the question
In order to leave comments, you need to log in
Why does Chrome consider request headers different (Link preload) even though they are identical?
The browser sees the header, loads the resource, but it is not used. The application makes its request again. The browser loads itself a version. JS loads its own.
A preload for is found, but is not used because the request headers do not match.
Link: URL; rel="preload"; as="fetch"; crossorigin="use-credentials",URL...
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question