Opened 8 years ago

Last modified 7 years ago

#4185 enhancement new

twisted.web.client.HTTPClient should expose the HTTP status as an integer

Reported by: Nathan Wilcox Owned by:
Priority: low Milestone:
Component: web Keywords:
Cc: Jean-Paul Calderone Branch:


The twisted.web.http.Request.setResponseCode() method requires an int argument to represent the HTTP status code to send to a client.

On the other hand, the twisted.web.client.HTTPClientFactory.deferred errback fires with a Failure whose .value.status contains a string representing the HTTP status code in the response from a server. (The errback fires when this status is an error status, such as a 404.)

I assumed I could pass the contents of a Failure to a Request (server-side response) but this raised a type error. A simplified example of the code would look like this:

def errback(reason):
    assert the_reason_represents_a_404_error_response(reason)

cfac = HTTPClientFactory('')
cfac.deferred.addCallbacks(normalHandler, errback)
reactor.connectTCP(, cfac.port, cfac)

Change History (4)

comment:1 Changed 8 years ago by Jean-Paul Calderone

Cc: Jean-Paul Calderone added
Priority: normallow
Summary: twisted.web.http and twisted.web.client handle HTTP status inconsistently.twisted.web.client.HTTPClient should expose the HTTP status as an integer

Aiming for this kind of symmetry is a great idea. For one thing, if a particular type makes sense on one side of the connection, it almost certainly makes sense on the other side. In this case, it certainly makes sense to represent the HTTP status as an integer; the server gets it right, the client gets it wrong. Fortunately, the new HTTP client gets it right and represents it as an integer.

I don't think this is something to fix in the older HTTP client though. Simply changing status to an integer is an incompatible change, so we should avoid that. We can add a new attribute and make that an integer... But that's a bit confusing and redundant, and considering all that's necessary to get the status as an integer is to use int on the existing attribute, may not be worthwhile.

If someone wants to implement this, or has another idea about how this might be improved, go for it. However, since it's so easy to "work around", and since there's a replacement for this API anyway, I don't think it's a big deal.

comment:2 Changed 7 years ago by Glyph

Actually, even in the new client, integer status codes are problematic; IIS apparently has some status codes with dots in them, although that's not spec-compliant.

We should probably have some kind of specific type used for HTTP status codes.

comment:3 Changed 7 years ago by jknight

I don't believe you. I think they only put those extended statuses in freetext parts of the response.

comment:4 Changed 7 years ago by <automation>

Owner: jknight deleted
Note: See TracTickets for help on using tickets.