Newer versions of requests library cause HTTP header issue
See original GitHub issueCurrentMediaStorageUsageInMB
: int, current attachment content (media) usage in MBs (Retrieved from gateway ).
HTTP headers in the latest versions of the request library cause the following error: requests.exceptions.InvalidHeader: Header value 0 must be of type str or bytes, not <class ‘int’>
Judging from a quick lookup in the code, the ‘CurrentMediaStorageUsageInMB’ value seems to be the culprit.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Troubleshoot a "Request header too large" message or 400 ...
The "Request header too large" message is thrown with an HTTP error code 400. This error occurs if the size of the request...
Read more >Cross-Origin Resource Sharing (CORS) - MDN Web Docs
Cross-Origin Resource Sharing (CORS) is an HTTP-header based mechanism that allows ... Additionally, for HTTP request methods that can cause ...
Read more >Community Updates — Requests 2.28.1 documentation
Fixed issue where non-UTF8 reason phrases got severely mangled by falling back to decoding using ISO 8859-1 instead. Fixed a bug where Requests...
Read more >"OverflowError: string longer than 2147483647 bytes ... - GitHub
In my case I have a 2GB+ POST request (not a file, just POST data). This is for an elasticsearch bulk update. The...
Read more >Python Requests Library: Up-To-Date 2022 Guide - Oxylabs
Python Requests Library is the most powerful tool for automating HTTP requests. Find out how to maximize common features of the Requests module...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We have fixed this issue in the Python SDK 2.1.0 release. Please let us know if you run into any issues.
The fix is checked in to our internal repo. I’ll get the release out in next few days.