Correctly implement credentialed CORS for the server #4513
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refer to #4511 for details.
This PR implements CORS for credentialed requests for the server. A credentialed request is when you send the Authorization header along with a request, some clients send an empty or placeholder API key because OpenAI requires one, whereas this server doesn't necessarily require one.
You can test that it works with this extremely simple client that implements both a regular client as well as one that sends an API key.
The server should still work with any other client in all scenarios.
I think it's worth making a list of clients this code has been tested against to ensure there are no regressions.