-
-
Notifications
You must be signed in to change notification settings - Fork 365
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
Add http 504 codes #367
Add http 504 codes #367
Conversation
Well, 208 was meant to be used with WebDAV, a technology Crow doesn't support. And AFAIK Crow doesn't have the proper mechanisms to return a 408 (Which shouldn't be something a Crow app manually reports). Can you elaborate on how you're using these 2 status codes? |
I should add that not returning a 408 isn't strictly in violation of the protocol. |
Hmm, for For |
For the second case I think returning a |
Agreed. Probably 504 makes more sense here. What do you think? |
It does, and there's precedent in it being there since 502 Bad Gateway is there already. |
0e0b214
to
ee4ccf7
Compare
Updated the PR with 504 code instead. |
Merged. Thank you for your help! |
Adding these extra status codes. Without these entries, if returned crow returns default 500, error code.