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

getHeader 204 response sets incorrect content-type header #268

Open
nflaig opened this issue Jul 19, 2024 · 0 comments
Open

getHeader 204 response sets incorrect content-type header #268

nflaig opened this issue Jul 19, 2024 · 0 comments

Comments

@nflaig
Copy link

nflaig commented Jul 19, 2024

In case case mev-rs receives no bid from any builder it will respond with 204 status code to a getHeader, this is as expected but it also sets content-type and content-length header while response payload does not contain JSON data.

These are the headers in 204 response

'content-type': 'application/json',
'content-length': '114'

but as the status code 204 - No Content implies, it shouldn't be sending any content, nor set a content type header

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

1 participant