-
Notifications
You must be signed in to change notification settings - Fork 174
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
cohttp-eio: Content-Type header #935
Comments
You don’t know a priori what is the content. I think we should leave it to the library users to do |
Yes, I agree. This is mostly a check point for me to check if |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://www.rfc-editor.org/rfc/rfc9110#section-8.3
Check Server and client include
Content-Type
headers as required.The text was updated successfully, but these errors were encountered: