Back to bug 1400632

Who When What Removed Added
Petr Pisar 2016-12-02 08:38:57 UTC Status NEW ASSIGNED
Petr Pisar 2016-12-02 10:57:28 UTC Keywords Patch
Petr Pisar 2016-12-02 11:47:14 UTC Keywords Regression
Petr Pisar 2016-12-02 11:51:43 UTC Summary with perl-libwww-perl-5.883-3 $env{https_proxy} ceases to be hounoured With perl-libwww-perl-5.883-3 https_proxy environment variable ceases to be honored by default
Joe Orton 2016-12-02 11:58:37 UTC CC jorton
Branislav Náter 2016-12-02 12:37:20 UTC CC bnater
Petr Pisar 2016-12-02 13:47:30 UTC Status ASSIGNED MODIFIED
Fixed In Version perl-libwww-perl-5.833-5.el6
Doc Text Cause:
Using a SOAP::Lite Perl module to send a SOAP request to
an HTTPS endpoint while an HTTP proxy is specified via
https_proxy environment variable and perl-libwww-perl
package is installed in 5.883-3 version.
Consequence:
The connection is established directly to the HTTPS
server instead via the HTTP proxy server.
Fix:
A code to LWP::UserAgent module was added that ensures
https_proxy and HTTPS_PROXY environment variables will
be honored even if no evn_proxy option was passed to
LWP::UserAgent's new() method. Also proxy specifications
without URL schema are recognized now.
Result:
A Net::SSL behavior regarding HTTPS proxy setting was
added to LWP::UserAgent so that applications used to
Net::SSL keep working even after a switch to
IO::Socket::SSL cryptographic back-end in
the perl-libwww-perl-5.883-3 package.
Doc Type If docs needed, set a value Release Note
errata-xmlrpc 2016-12-02 13:51:43 UTC Status MODIFIED ON_QA
Branislav Náter 2016-12-02 17:02:54 UTC QA Contact qe-baseos-apps mkyral
Lenka Špačková 2016-12-12 11:17:00 UTC Docs Contact lkuprova
Martin Kyral 2016-12-16 08:30:35 UTC Status ON_QA VERIFIED
Lenka Špačková 2016-12-20 13:52:58 UTC Doc Text Cause:
Using a SOAP::Lite Perl module to send a SOAP request to
an HTTPS endpoint while an HTTP proxy is specified via
https_proxy environment variable and perl-libwww-perl
package is installed in 5.883-3 version.
Consequence:
The connection is established directly to the HTTPS
server instead via the HTTP proxy server.
Fix:
A code to LWP::UserAgent module was added that ensures
https_proxy and HTTPS_PROXY environment variables will
be honored even if no evn_proxy option was passed to
LWP::UserAgent's new() method. Also proxy specifications
without URL schema are recognized now.
Result:
A Net::SSL behavior regarding HTTPS proxy setting was
added to LWP::UserAgent so that applications used to
Net::SSL keep working even after a switch to
IO::Socket::SSL cryptographic back-end in
the perl-libwww-perl-5.883-3 package. 		The *LWP::UserAgent* and *SOAP::Lite* Perl modules now correctly handle proxy settings for HTTPS requests

The *LWP::UserAgent* and the *SOAP::Lite* Perl modules previously did not honor environment variables by default. The _perl-libwww-perl_ package version 5.883-3 started using the *IO::Socket::SSL* module instead of the *Net::SSL* module for implementing TLS. When using the *SOAP::Lite* module to send a Simple Object Access Protocol (SOAP) request to an HTTPS endpoint while an HTTP proxy was specified using the `https_proxy` environment variable and the _perl-libwww-perl_ package version 5.883-3 was installed, the connection was established directly to the HTTPS server instead of through the HTTP proxy server. With this update, the *Net::SSL* module's behavior has been added to the *LWP::UserAgent* module to ensure that the `https_proxy` and `HTTPS_PROXY` environment variables are honored even if no `evn_proxy` option was passed to the *LWP::UserAgent* module's `new()` method. Additionally, proxy specifications without a URL schema are recognized now. As a result, applications using the *Net::SSL* module correctly work after switching to the *IO::Socket::SSL* cryptographic back end from the _perl-libwww-perl_ package.
Lenka Špačková 2016-12-20 15:43:39 UTC Doc Text The *LWP::UserAgent* and *SOAP::Lite* Perl modules now correctly handle proxy settings for HTTPS requests

The *LWP::UserAgent* and the *SOAP::Lite* Perl modules previously did not honor environment variables by default. The _perl-libwww-perl_ package version 5.883-3 started using the *IO::Socket::SSL* module instead of the *Net::SSL* module for implementing TLS. When using the *SOAP::Lite* module to send a Simple Object Access Protocol (SOAP) request to an HTTPS endpoint while an HTTP proxy was specified using the `https_proxy` environment variable and the _perl-libwww-perl_ package version 5.883-3 was installed, the connection was established directly to the HTTPS server instead of through the HTTP proxy server. With this update, the *Net::SSL* module's behavior has been added to the *LWP::UserAgent* module to ensure that the `https_proxy` and `HTTPS_PROXY` environment variables are honored even if no `evn_proxy` option was passed to the *LWP::UserAgent* module's `new()` method. Additionally, proxy specifications without a URL schema are recognized now. As a result, applications using the *Net::SSL* module correctly work after switching to the *IO::Socket::SSL* cryptographic back end from the _perl-libwww-perl_ package. 		The *LWP::UserAgent* Perl module now correctly handles proxy settings for HTTPS requests

The *LWP::UserAgent* Perl module previously did not honor HTTPS proxy environment variables by default. The _perl-libwww-perl_ package version 5.883-3 started using the *IO::Socket::SSL* module instead of the *Net::SSL* module for implementing TLS. Consequently, applications relying on processing of the `https_proxy` environment variable in the *Net:SSL* module established connections directly to the HTTPS server instead of through the HTTPS proxy server.

With this update, the *Net::SSL* module's behavior has been added to the *LWP::UserAgent* module to ensure that the `https_proxy` and `HTTPS_PROXY` environment variables are honored if no `env_proxy` option has been passed to the *LWP::UserAgent* module's `new()` method. Additionally, proxy specifications without a URL schema are recognized now. As a result, applications using the *Net::SSL* module correctly work after switching to the *IO::Socket::SSL* cryptographic back end from the _perl-libwww-perl_ package.
Lenka Špačková 2016-12-22 15:30:07 UTC Doc Text The *LWP::UserAgent* Perl module now correctly handles proxy settings for HTTPS requests

The *LWP::UserAgent* Perl module previously did not honor HTTPS proxy environment variables by default. The _perl-libwww-perl_ package version 5.883-3 started using the *IO::Socket::SSL* module instead of the *Net::SSL* module for implementing TLS. Consequently, applications relying on processing of the `https_proxy` environment variable in the *Net:SSL* module established connections directly to the HTTPS server instead of through the HTTPS proxy server.

With this update, the *Net::SSL* module's behavior has been added to the *LWP::UserAgent* module to ensure that the `https_proxy` and `HTTPS_PROXY` environment variables are honored if no `env_proxy` option has been passed to the *LWP::UserAgent* module's `new()` method. Additionally, proxy specifications without a URL schema are recognized now. As a result, applications using the *Net::SSL* module correctly work after switching to the *IO::Socket::SSL* cryptographic back end from the _perl-libwww-perl_ package. 		The *LWP::UserAgent* Perl module now correctly handles proxy settings for HTTPS requests

The *LWP::UserAgent* Perl module previously did not honor HTTPS proxy environment variables by default. The _perl-libwww-perl_ package version 5.883-3 started using the *IO::Socket::SSL* module instead of the *Net::SSL* module for implementing TLS. Consequently, applications relying on processing of the `https_proxy` environment variable in the *Net:SSL* module established connections directly to the HTTPS server instead of through the HTTPS proxy server.

With this update, the *Net::SSL* module's behavior has been added to the *LWP::UserAgent* module to ensure that the `https_proxy` and `HTTPS_PROXY` environment variables are honored if no `env_proxy` option has been passed to the *LWP::UserAgent* module's `new()` method. Additionally, proxy specifications without a URL schema are now recognized. As a result, applications using the *Net::SSL* module correctly work after switching to the *IO::Socket::SSL* cryptographic back end from the _perl-libwww-perl_ package.
Lenka Špačková 2017-02-16 13:37:37 UTC Doc Text The *LWP::UserAgent* Perl module now correctly handles proxy settings for HTTPS requests

The *LWP::UserAgent* Perl module previously did not honor HTTPS proxy environment variables by default. The _perl-libwww-perl_ package version 5.883-3 started using the *IO::Socket::SSL* module instead of the *Net::SSL* module for implementing TLS. Consequently, applications relying on processing of the `https_proxy` environment variable in the *Net:SSL* module established connections directly to the HTTPS server instead of through the HTTPS proxy server.

With this update, the *Net::SSL* module's behavior has been added to the *LWP::UserAgent* module to ensure that the `https_proxy` and `HTTPS_PROXY` environment variables are honored if no `env_proxy` option has been passed to the *LWP::UserAgent* module's `new()` method. Additionally, proxy specifications without a URL schema are now recognized. As a result, applications using the *Net::SSL* module correctly work after switching to the *IO::Socket::SSL* cryptographic back end from the _perl-libwww-perl_ package. 		The *LWP::UserAgent* Perl module now correctly handles proxy settings for HTTPS requests

The *LWP::UserAgent* Perl module previously did not honor HTTPS proxy environment variables by default. The _perl-libwww-perl_ package version 5.883-3 started using the *IO::Socket::SSL* module instead of the *Net::SSL* module for implementing TLS. Consequently, applications that rely on processing of the `https_proxy` environment variable in the *Net:SSL* module established connections directly to the HTTPS server instead of through the HTTPS proxy server.

With this update, the *Net::SSL* module's behavior has been added to the *LWP::UserAgent* module to ensure that the `https_proxy` and `HTTPS_PROXY` environment variables are honored if no `env_proxy` option has been passed to the *LWP::UserAgent* module's `new()` method. Additionally, proxy specifications without a URL schema are now recognized. As a result, applications using the *Net::SSL* module correctly work after switching to the *IO::Socket::SSL* cryptographic back end from the _perl-libwww-perl_ package.
errata-xmlrpc 2017-03-21 00:30:43 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-03-21 09:25:44 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-03-21 05:25:44 UTC
vani 2018-06-12 15:27:49 UTC CC sivavani.basetty

Back to bug 1400632