This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dsoprea
Recipients Dustin.Oprea, dsoprea, pitrou, r.david.murray
Date 2014-11-11.14:43:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAOr1xOF-8UTeJ7am3YRQqWTiPC_NUkW3xu2d4PQfiasJWN7Lrw@mail.gmail.com>
In-reply-to <5461DA3A.1020300@free.fr>
Content
I usually use both on my local system.

Dustin
On Nov 11, 2014 4:43 AM, "Antoine Pitrou" <report@bugs.python.org> wrote:

>
> Antoine Pitrou added the comment:
>
> Le 11/11/2014 07:50, Dustin Oprea a écrit :
> >
> > Dustin Oprea added the comment:
> >
> > I think I was getting mixed results by using requests and urllib2/3.
> After nearly being driven crazy, I performed the following steps:
> >
> > 1. Recreated client certificates, and verified that the correct CA was
> being used from Nginx.
> >
> > 2. Experimenting using an SSL-wrapped client-socket directly, in tandem
> with s_client.
> >
> > 3. I then removed all of my virtualhosts except for a new one that
> pointed to a flat directory, just to make sure that I wasn't activating the
> wrong virtualhost, and there weren't any other complexities.
> >
> > 4. Implemented a bonafide, signed, SSL certificate on my local system,
> and overriding the hostname using /etc/hosts.
> >
> > 5. This got me past the 400.
>
> Ah! Perhaps your HTTPS setup was relying on SNI to select the proper
> virtual host ?
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue22835>
> _______________________________________
>
History
Date User Action Args
2014-11-11 14:43:25dsopreasetrecipients: + dsoprea, pitrou, r.david.murray, Dustin.Oprea
2014-11-11 14:43:25dsoprealinkissue22835 messages
2014-11-11 14:43:25dsopreacreate