[lxml-dev] Failure with custom resolvers and relative xsl:import

[Eric Tiffany]

I have used M2Crypto for clientTLS connections from MacOS, Ubuntu, and
Vista, all using the same codebase (including LXML) running under Plone.

Works brillantly.

ET

On 8/19/08 11:07 AM, "John Lovell" <jlovell at esd189.org> wrote:

> Stefan:
> 
> So what is your "preferred Python HTTPS client library?"  I recently
> tried very hard and ultimately failed at handling https cross platform
> with Python.
> 
> Thanks for all you do,
> 
> John W. Lovell
> Web Applications Engineer
> Northwest Educational Service District
> 1601 R Avenue
> Anacortes, WA 98221
> (360) 299-4086
> jlovell at nwesd.org
>  
> www.nwesd.org
> Together We Can ...
> 
> 
> -----Original Message-----
> From: Stefan Behnel [mailto:stefan_ml at behnel.de]
> Sent: Tuesday, August 19, 2008 3:38 AM
> To: John Lovell
> Cc: ML-Lxml-dev
> Subject: Re: [lxml-dev] Failure with custom resolvers and relative
> xsl:import
> 
> John Lovell wrote:
>> If you find a currently maintained pure Python way to add SSL, please
>> let us know.
> 
> Hmmm, isn't it enough to use a custom resolver to intercept only
> "https://..." requests (return None for everything else) and to redirect
> them to your preferred Python HTTPS client library?
> 
> I'm not sure implementing this directly in lxml makes sense, as it
> wouldn't allow using certificates and these things. But it shouldn't be
> too hard to do on your own.
> 
> Stefan
> 
> _______________________________________________
> lxml-dev mailing list
> lxml-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/lxml-dev

-- 
________________________________________________
Eric  Tiffany           | +1 413-458-3743
etiffany at alum.mit.edu   | +1 413-627-1778 mobile