Statuscat 418 doesn't work
See original GitHub issueDescription
Http code 418 is reported to be invalid, even though its defined here. A cat exists for the status code too.
Steps to Reproduce
Send .statuscat 418
to Seasonalbot.
Expected Behaviour
Sends an embed with this image in it, and a header of Status: 418
.
Actual Behaviour
Code not found:
Known Impacted Platforms
- Web
- Desktop
- Android App
- iOS App
Possible Solutions
Check for status code 418 before checking for the other codes the http library.
Would you like to implement a fix?
Note: For high-priority or critical bugs, fixes may be implemented by staff.
- I’d like to implement the bug fix
- Anyone can implement the bug fix
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (14 by maintainers)
Top Results From Across the Web
418 I'm a teapot - HTTP - MDN Web Docs
The HTTP 418 I'm a teapot client error response code indicates that the server refuses to brew coffee because it is, permanently, a...
Read more >HTTP Status Code 418 not recognized by .http_status command ...
Description The .http_status .status and .httpstatus commands do not recognize HTTP status code 418 (I am a Teapot) as described in RFC-2324 :...
Read more >How to return status code 418 in Webapp2 - Stack Overflow
By monkey patching, I am able to get the status code 418 to work, but only partially. class TeapotHandle(webapp2.
Read more >418 I'm a Teapot - HTTP Status Code Glossary - WebFX
Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY...
Read more >418 HTTP Status Code: Im a teapot! - DEV Community
The HTTP 418 I'm a teapot client error response code indicates that the server refuses to brew coffee because it is a teapot....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We will update to 3.9 when the libraries we are using will be ready and at least one patch of CPython will have been released. 🙂
This issue has been usurped by #608, and a solution is already in place in PRs.