Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove '{}' payload from cors OPTIONS response #2359

merged 1 commit into from Jan 22, 2015


Copy link

@kanongil kanongil commented Jan 22, 2015

While I guess the payload is allowed, it is quite redundant and adds a content-type header.

Copy link

@ghost ghost commented Jan 22, 2015

Oh that's a nice one!

@hueniverse hueniverse added bug and removed feature labels Jan 22, 2015
@hueniverse hueniverse self-assigned this Jan 22, 2015
@hueniverse hueniverse added this to the 8.2.0 milestone Jan 22, 2015
hueniverse pushed a commit that referenced this issue Jan 22, 2015
Remove '{}' payload from cors OPTIONS response
@hueniverse hueniverse merged commit c3e211b into hapijs:master Jan 22, 2015
1 check passed
Copy link

@lock lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants