Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Content-Type header present when responding with 204
See original GitHub issue-
I’m submitting a … [ X ] bug report [ ] feature request [ ] question about the decisions made in the repository
-
Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
When setting the response status via cherrypy.response.status to 204 the Content-Type header is still present.
- What is the expected behavior?
No Content-Type header when there is no content with a 204 status code
- What is the motivation / use case for changing the behavior?
Some clients and test frameworks (i.e WebTest: https://pypi.python.org/pypi/WebTest) will error when there is a Content-Type with status code 204.
- Please tell us about your environment:
- Cheroot version: 5.8.3
- CherryPy version: 11.0.0
- Python version: 3.6.2
- OS: Windows 10
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yup looks good in cheroot 6 and cherrypy 13.1
Cool, thanks for checking. I’ve also noticed that we actually have a test for this: https://github.com/cherrypy/cheroot/blob/5bc7b39/cheroot/test/test_conn.py#L579-L584 (JFI)