[Twisted-web] HTTP(S) Client with authentication support

Jean-Paul Calderone exarkun at divmod.com
Mon Mar 3 00:25:24 EST 2008


On Sun, 02 Mar 2008 20:00:16 +0000, Bruno Harbulot <bruno.harbulot at manchester.ac.uk> wrote:
>Hello,
>
>I'm new to Twisted, and I'd like to know if there is any HTTP(S) Client API 
>that would support various authentication methods and strategies. By 
>'strategy', I mean that, ideally, the client application could define some 
>sort of 'strategies' to tell the client API what to reply when challenged 
>with an HTTP 401 Unauthorized response code.
>I guess that's feasible using HTTP Basic authentication, but I'd also like 
>to be able to define when to send a client certificate for authentication to 
>an HTTPS server than wants or requires it.
>Could some of these goals be achieved with Twisted.Web or Twisted.Web2? I'm 
>not sure where to find documentation on the subject. I'd appreciate any 
>pointers or suggestions.

Support for authentication in twisted.web.client isn't very strong.  This
kind of thing would best be done by adding a a more flexible client API.

Jean-Paul



More information about the Twisted-web mailing list