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.

Sign up for GitHub

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

Jump to bottom

[🐛 | Bug]: Incorrect content-type header when client uses anonymous rpc api #2979

Closed
touilleMan opened this issue Aug 31, 2022 · 0 comments · Fixed by #2544
Closed

[🐛 | Bug]: Incorrect content-type header when client uses anonymous rpc api #2979

touilleMan opened this issue Aug 31, 2022 · 0 comments · Fixed by #2544
Assignees
@touilleMan
Labels
C-Bug Issue related to a bug

Comments

@touilleMan
Copy link
Member

touilleMan commented Aug 31, 2022 •
edited
Loading

Version

<=2.11.1

What happened ?

According to urlib.request.Request documentation:

An appropriate Content-Type header should be included if the data argument is present. If this header has not been provided and data is not None, Content-Type: application/x-www-form-urlencoded will be added as a default.

So we currently send application/x-www-form-urlencoded as content type instead of application/msgpack
@touilleMan touilleMan added the C-Bug Issue related to a bug label Aug 31, 2022
@touilleMan touilleMan linked a pull request Aug 31, 2022 that will close this issue
Feat/authenticated api server #2544
Merged
23 tasks
@touilleMan touilleMan self-assigned this Aug 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@touilleMan touilleMan

Labels
C-Bug Issue related to a bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feat/authenticated api server Scille/parsec-cloud
1 participant
@touilleMan