Incorrect status_code - response returning 'HTTP/1.1 200 OK' #393
Closed
maRT-sk
started this conversation in
Potential Issue
Replies: 2 comments 3 replies
-
@maRT-sk hmm! Weird. Let us investigate this. Next week we have a release planned and if this is an issue after investigation, it will also be fixed there. But before anything else, can you do this: @get(status_code=status. HTTP_202_ACCEPTED) And let us know if the error still persists, please? |
Beta Was this translation helpful? Give feedback.
3 replies
-
Addressed |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am encountering an issue where the response status_code is always returned as
HTTP/1.1 200 OK
, despite other status codes being specified and expected.Steps to Reproduce
Expected Behavior: The response should return a
HTTP/1.1 202 Accepted
status code as specified in the response.Actual Behavior: The response status code is
HTTP/1.1 200 OK
, regardless of the specified status code.Additional Information
This issue was reproduced on the following setups:
Please let me know if you need any further information.
Questions
Is there something I might be overlooking? Could this be related to my specific environment setup, or is it a broader issue?
When I comment out the following lines of code in the Esmerald source, the correct status codes are returned:
esmerald/routing/base.py#L297-L298
Beta Was this translation helpful? Give feedback.
All reactions