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

More HTTP methods are required #7

Closed
cherepets opened this issue Apr 26, 2017 · 2 comments
Closed

More HTTP methods are required #7

cherepets opened this issue Apr 26, 2017 · 2 comments

Comments

@cherepets
Copy link
Contributor

HTTP methods like OPTIONS, HEAD, TRACE and CONNECT are a part of the rfc so it's good to have them.
In some cases (mostly jsonp) Chrome web browser can replace POST with OPTIONS so we definitely need to allow OPTIONS to have content.
As far as I know custom methods also can have content.

@cherepets
Copy link
Contributor Author

cherepets commented Apr 26, 2017

Created a pull request for this:
#8

@StefH
Copy link
Owner

StefH commented Apr 27, 2017

Thanks.

@StefH StefH closed this as completed Apr 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants