Skip to content

Conversation

noxxi
Copy link
Contributor

@noxxi noxxi commented Nov 9, 2013

Hi,
this change fixes the behavior of https_proxy.
Current behavior: send unencrypted requests with https:// URLs to specified proxy
Correct behavior: create encrypted tunnel to proxy and send requests within
This is part#2 of the change, the rest is in libwww-perl

Regards,
Steffen Ullrich (maintainer IO::Socket::SSL)

This goes together with change to libwww-perl cb80c2ddb7
- new method _upgrade_sock in LWP::Protocol::https, but only if the
  default SSL library IO::Socket::SSL is used (e.g. can start_SSL).
  This enables LWP::Protocol::http to establish tunnel and upgrade an
  existing socket.
- extensive test t/https_proxy.t to make sure that LWP behaves
  correctly. test can be run with IO::Socket::SSL and Net::SSL as
  backend by forcing library with environment
  PERL_NET_HTTPS_SSL_SOCKET_CLASS
gisle added a commit that referenced this pull request Nov 21, 2013
fix https_proxy problem for IO::Socket::SSL and Net::SSL, includes extensive test (Part#2)
@gisle gisle merged commit 9b568ed into libwww-perl:master Nov 21, 2013
@dod38fr
Copy link

dod38fr commented Nov 22, 2013

@gisle thanks for the merge.

Could you publish a new release for libwww-perl and lwp-protocol-https ?

Once this is done, we will be able to close a lot of bug in Debian that are plaguing users stuck behind a firewall. (I'm pretty sure that other distros are in a similar situation)

All the best

@bluescreen10
Copy link

@gisle Do you have a target date for publishing this to CPAN?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants