#CORS Exception
12 messages · Page 1 of 1 (latest)
@misty breach i investigated a bit more and even i, with a key that has credits, get the same error regardless of whether it's mistral, gpt-4, .... browser choice (chrome, firefox) also doesn't matter.
The options request returns a 401 because it doesn't contain the auth header (that only gets sent via POST). So kind of similar to https://discord.com/channels/1091220969173028894/1164663380276154438
I'm not a super specialist, but as far as I know this is usually cured by API providing "Allow-Cross-Aceess-Origin: *" header or something like that.
So that allows browsers to understand that this API might be called from different hosts
We do that, but we need to special-case OPTIONS requests. This involves changing around some things - testing a fix now
all right, should be fixed now
!
Think we broke this midway today during the DoS craziness - looking into a way of testing for it from command-line tests
thanks a bunch! not getting any error reports right now 😊