You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Hajk is deployed behind an authentication proxy, requests for the manifest.json fails with a 401.
My guess is that this stems from the fact that no crossorigin-attribute is set on the link. Adding crossorigin="use-credentials" seems to fix the error.
Suggested fix: Add crossorigin="use-credentials" on the manifest-links (both in client and admin).
The text was updated successfully, but these errors were encountered:
Is this treated differently because of the MIME type? You haven't seen the same problems with the remaining resources (logo192.png, index.css)? Otherwise it could be a good time to fix that now too.
If Hajk is deployed behind an authentication proxy, requests for the
manifest.json
fails with a 401.My guess is that this stems from the fact that no crossorigin-attribute is set on the link. Adding
crossorigin="use-credentials"
seems to fix the error.Suggested fix: Add
crossorigin="use-credentials"
on the manifest-links (both in client and admin).The text was updated successfully, but these errors were encountered: