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

Status Code strings #22

Closed
nhumrich opened this issue Nov 30, 2016 · 5 comments
Closed

Status Code strings #22

nhumrich opened this issue Nov 30, 2016 · 5 comments

Comments

@nhumrich
Copy link

Currently the status code header on the response object from the server only includes the status code number and not the string. This does not follow the HTTP spec.

Returns:

HTTP/1.1 200

Should return

HTTP/1.1 200 OK

Is there currently anyway to add the OK string on the response?

@nhumrich
Copy link
Author

Nevermind, I see the reason arg now.

@njsmith
Copy link
Member

njsmith commented Nov 30, 2016 via email

@nhumrich
Copy link
Author

nhumrich commented Dec 4, 2016

I'd accept a patch that set the default reason based on the status using the table in Python's built-in http package

I like this idea. I will work on this.

I am building an microservice async framework that works with asycio/curio.

if there are things that annoy you

I mostly finished the http portion, so if there was anything, I dont remember now 😄 but ill let you know if I find anything.

Thanks.

@njsmith
Copy link
Member

njsmith commented Dec 5, 2016

I am building an microservice async framework that works with asycio/curio.

Neat! Is it open source?

You'll still want to subscribe to #17 if you haven't -- there will probably be a few hopefully-small-but-still breaking changes in h11 ahead. (In particular I think we need to do something better about handling request targets.)

@nhumrich
Copy link
Author

nhumrich commented Dec 5, 2016

https://github.com/wickedasp/wasp

Curio support will probably happen later once curio is out of alpha.

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