I just finished replacing httplib in a very large project, Apache Libcloud.

When httplib was selected, requests wasn’t around (it only hit v1 in 2012). We needed to provide a set of base classes that would handle HTTP and HTTPS REST/JSON, REST/XML and various other bizarre HTTP APIs. Libcloud has over 80 client libraries for every major cloud service out there. Each of those libraries share a single Connection class that handles encoding and decoding of JSON, XML or Raw data. Whipping the tablecloth out from under our diners was going to be tricky. Especially having experienced first hand how awful some APIs are (see related post) I was tentative that this could be done without knock on issues for our users. Libcloud has excellent test coverage, with each driver typically having around 90% and the base utilities are tested with all expected and supported behaviours across all major version of Python 2 and 3.

Making requests in requests

There are a few ways to make HTTP/HTTPS requests in requests. Firstly, it is worth noting that in httplib, you have to spend a lot of time deciding how you would handle TLS or SSL decryption and trust for HTTPS endpoints.

This is no longer the case in requests. The abstraction of HTTPS handling, for us was the big appeal and also for our users.

This is actually just a friendly wrapper around the main request method with the HTTP verb as the first argument. I have seen some bad examples of people writing long if/elif/elif around the HTTP Verb but request is part of the main API.

Requests seems to have modelled a lot of it’s API around a web browser. You can set things like cookies, redirect, HTTPS is handled cleanly.

Calling requests.request in turn creates a Session. If you are making multiple requests to the same endpoint you are better to use a session since it will hold open the TCP session between connections, keep a cookie jar and also remember any preferences for each request.

All of the APIs that Libcloud talks to have some form of authentication, perhaps Basic HTTP (base 64 username/password), OAuth, API keys. All of these would require configuration of custom headers for the lifetime of the session, so we decided early to leverage the requests Session object for all requests. So now each Libcloud driver connection will have it’s own Session in the background. I realised early on that whilst the high-level APIs were great for a single request, I needed to get more familiar with the way requests operates to get the outcome I needed. If you use requests often, read on.

Understanding the Session object

I often see code snippets like this, ignoring sessions and the JSON-native features.

Providing a dictionary to json argument will encode the data for you, using a Session context-manager you can set default headers by the headers property.

Within the Session initialiser it will assign a set of default headers including the flags to allow gzip responses and use keep-alive. Avoid setting sess.headers to a new dictionary, especially since the default property is a case-insensitive dictionary which comes in mighty-handy doing lookups.

Understanding PreparedRequest

When you keep peeling back the onion, Session.request creates an instance of the PreparedRequest object. You can construct these objects by hand, typically when you have a specific binary payload to send and set of headers.

Handling large requests, streams and iterators

If you’re uploading or downloading large requests or responses, requests provides some utilities for working with streams or generic iterators.

Uploading with streams

Requests will detect when the data argument is an iterator like a file stream object or a BytesIO or StringIO stream.

Downloading with streams

Making a request with the stream flag will allow iter_content on the Response object to iterate the data from an open connection. iter_content will still work without stream, but it will download the response into memory first (probably doubling the execution time to achieve the same result).