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
As the title says, when loading a sample with useOgvFallback enabled, I get this error in my console:
Refused to get unsafe header "Content-Range"
As far as I can tell, this is a CORS-related issue. I might also be the first person to have this issue, since I'm running the soundboard frontend locally but using the production API. I guess that when they're running on the same origin, there's no CORS issues.
I think it could be fixed by adding this header: Access-Control-Expose-Headers: Content-Range.
Hmm. I've tested OGV.js plenty from local to real API and on Safari as well and never ran into this somehow. I'll try to reproduce.
Also I have some concerns with the 3.0 tag. I get the reference to editor 3.0, but the soundboard's already passed v3.0 a while ago. Shouldn't it be v4.0? And wouldn't this cause PTSS for you every time you see the tag? =O
As the title says, when loading a sample with
useOgvFallback
enabled, I get this error in my console:As far as I can tell, this is a CORS-related issue. I might also be the first person to have this issue, since I'm running the soundboard frontend locally but using the production API. I guess that when they're running on the same origin, there's no CORS issues.
I think it could be fixed by adding this header:
Access-Control-Expose-Headers: Content-Range
.See also this line in
stream-file
(the library used byogv.js
): https://github.com/brion/stream-file/blob/d1b41ca2992b908d8910d5389b6a663146d5d5b3/src/backend/backend.js#L30The text was updated successfully, but these errors were encountered: