Implements CORS headers, and shared Content-Type #1
Conversation
This file contains 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
Contributor
skinkie
commented
Jan 15, 2012
skinkie
commented
- Some README updates for the current eJabberd.
|
Probably need a setting to turn CORS on/of and configure which domains are allowed to do CORS. |
|
This is very cool and thanks. I'll merge it once there is a way to turn CORS off. I would hate to have this be the default setting as others might not want to open up the pre bind to all requests. |
|
You know that the default setting of ejabberd is to allow all? And it being hardcoded? I wouldn't know why you would like to be stricter than the server you are working from. |
|
Looks like ejabberd needs to be changed too. :) |
thepug
added a commit
that referenced
this pull request
Jan 15, 2012
Implements CORS headers, and shared Content-Type
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.