-
Notifications
You must be signed in to change notification settings - Fork 1k
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
OPTIONS generated by CORS doesn't work correctly in local #525
Comments
Yep this looks like a bug to me. HTTP 1.1 defaults to not closing the connection unless the Edit: To follow up on that, when I try this locally it hangs on the first OPTIONS request. I can't replicate getting the first one to succeed. |
I'm seeing this OPTIONS behavior when |
First of all, thank you for this awesome framework. Really easy to use, I like it a lot.
I'm developing an API that has to accept CORS and i'm having troubles with the OPTIONS methods.
The problem is easy to reproduce:
In app.py
Then, run it in local:
chalice local --port=8100
When you try to do the first OPTIONS curl, everything works =)
Response:
But the next OPTIONS curl will not end never =(
It stops in
* no chunk, no close, no size. Assume close to signal end
. It seems like the server only send the close signal only in the first call. If you stop the second curl and try it again, it wont stop neither.Do you have the same problem? Can you reproduce it?
P.S.: I'm using macOS, but I hope that is not a problem to do the local development =P
The text was updated successfully, but these errors were encountered: