requests
                                
                                
                                
                                    requests copied to clipboard
                            
                            
                            
                        A simple, yet elegant, HTTP library.
While looking for an asyncio compatible recommendation for requests, I stumbled on the [documentation](https://requests.readthedocs.io/en/latest/community/recommended/) provided by the project. It recommends Request-Threads, which does not seem to be actively developed (no...
See bug #6294 for original bug report. This PR provides a possible fix for this, reverting the change in #2896. The change in #2896 definitely causes some bad side effects,...
This is a possible fix for issue #6586. I am not at all confident that this is an appropriate change for Requests. All of the unit tests pass locally for...
When a server sends less bytes than indicated by Content-Length, we get a ChunkedEncodingError instead of retrying the request. urllib3 supports retrying requests in this situation by setting `preload_content=True`. When...
Added a fix for the issue mentioned here - https://github.com/psf/requests/issues/6223 Checked in the code, only one package of chardet was being mapped to requests.packages.chardet despite the for loop. Have added...
Have added the fix for the issue mentioned here - https://github.com/psf/requests/issues/6557 Since empty lists, dicts, tuples aren't of none type they should be added in the url string.
The `Response.iter_lines` method is seriously broken (it inserts fake blank lines in unpredictable places.) The earliest report of this I've found is pull #2431 (January 2015). The behavior was apparently...
Hi, I noticed a broken link to rfc2988 in the [timeout section of the docs](https://requests.readthedocs.io/en/latest/user/advanced/#timeouts) and thought I would fix it. While doing that, I thought I would run the...
There are two tests here. One demonstrating existing, correct behavior for `data=bytes`, and another, failing, test for the case where `data=string` and the string contains multi-byte UTF-8.
TLDR: On some libc implementations (e.g. glibc) the `socket.inet_aton` function parses IP strings trailed with whitespace and garbage, and this function is used by requests utility functions which if used...