Access-Control-Allow-Origin header must be included in all valid CORS responses#1195
Open
Zatvobor wants to merge 1 commit into
Open
Access-Control-Allow-Origin header must be included in all valid CORS responses#1195Zatvobor wants to merge 1 commit into
Zatvobor wants to merge 1 commit into
Conversation
Zatvobor
changed the title
Contributor
|
Hi @Zatvobor It would be really nice to be able to merge this PR but unfortunately almost all Travis jobs fail. Could you please modify integration tests accordingly? |
Contributor
|
Hi @Zatvobor Are you perhaps to rebase and finalise this PR? Some new tests will be welcome as well. :) |
|
I'm having problems with chat clients connecting via BOSH over https. The CORS headers are not being sent, at least they are not always being sent. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR addresses #1045