Closed pheyvaer closed 5 months ago
The HEAD request is coming from following workaround, this is to support ESS, but this shouldn't affect CSS pods. https://github.com/redpencilio/ember-solid/blob/experimental/ess-support/addon/utils/forking-store.js#L115-L122 It's weird that you're experiencing this bug as I cannot reproduce it myself.
I'm getting the same CORS error with my id.inrupt.com pod, but this doesn't give me a blank page. Maybe something else is still causing that blank page.
The internal architecture changed drastically, do you still experience this issue @pheyvaer ?
Closing this issue for now. Feel free to reopen if you would still experience the same issue.
After logging in, I get a blank page and there is the following error in the console
Looking at the network information, the error is coming from a HEAD request to my WebID. I'm using FireFox Developer Edition 110.0b9 (64-bit). This error doesn't happen when using Chrome 109.0.5414.119.
I know that my server/pod doesn't set CORS headers for HEAD requests. but why should it? I've never seen HEAD request being mentioned in CORS discussions.