Add CORS headers to dream server to ease integration with third-party web interfaces #363
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.
I am tinkering on a project that explores some additional functionality for the web interface such as prompt queueing. Projects like these (where dev servers and deployed versions run on a different host or port than the stable-diff embedded web server) are currently suffering from failing preflight requests and additional CORS errors, since the server does not provide appropriate header responses.
This PR adds the
Access-Control-Allow-OriginandAccess-Control-Allow-HeadersCORS headers to the appropriate responses, as well as adds theOPTIONHTTP method for preflight requests.