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

Use Access-Control-Allow-Methods instead of Allow for CORS #27

Closed
majek opened this Issue Dec 8, 2011 · 1 comment

Comments

Projects
None yet
1 participant
@majek
Member

majek commented Dec 8, 2011

http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.7

says that 405 requires Allow header. But this isn't a good header for OPTIONS request:

http://www.w3.org/TR/cors/#access-control-allow-methods-response-he

We should make sure we adhere to specs.

@majek

This comment has been minimized.

Show comment
Hide comment
@majek
Member

majek commented Dec 8, 2011

@majek majek closed this in a59141d Dec 19, 2011

majek added a commit to sockjs/sockjs-node that referenced this issue Jan 19, 2012

majek added a commit that referenced this issue Jan 19, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment