Edit report at http://bugs.php.net/bug.php?id=44248&edit=1
ID: 44248
Updated by: dmi...@php.net
Reported by: jboffel at gmail dot com
Summary: RFC2616 transgression while HTTPS request through
proxy with SoapClient object
-Status: Assigned
+Status: Closed
Type: Bug
Package: SOAP related
Operating System: Linux RedHat Enterprise
PHP Version: 5.2.9
Assigned To: dmitry
Block user comment: N
New Comment:
This bug has been fixed in SVN.
Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
Thank you for the report, and for helping us make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2010-10-05 13:44:01] dmi...@php.net
Automatic comment from SVN on behalf of dmitry
Revision: http://svn.php.net/viewvc/?view=revision&revision=304084
Log: Fixed bug #44248 (RFC2616 transgression while HTTPS request through
proxy with SoapClient object).
------------------------------------------------------------------------
[2009-09-10 08:29:50] sjo...@php.net
Dmitry, you seem to be the expert on SOAP/HTTP connecting. Can you take
this bug?
------------------------------------------------------------------------
[2009-09-09 20:55:53] jboffel at gmail dot com
Did you test to use Apache like web server or like proxy ?
I had problem when used like proxy with Apache 1.3
You should get a 400 Bad Request error status code...
The only case it could not return error is if the host is in fact an IP.
In that case host parameter is supposed to be sent empty so it's
possible they decided to accept without complaining requests in this
particular case.
------------------------------------------------------------------------
[2009-09-09 19:46:28] sjo...@php.net
Could reproduce. The SoapClient does indeed not send a Host parameter
when doing a CONNECT, which is a bug because the RFC says it should.
However, this causes no problems with any version of Apache I tried
(1.3, 2.0, 2.2).
------------------------------------------------------------------------
[2009-09-01 18:55:53] jboffel at gmail dot com
The thing is that Apache server follow the RFC and really block
(voluntarily that is not a bug) the request (there is no workaround to
force Apache to do the job or I didn't find it). You can see in the
error log file that Apache ask us to follow the RFC and add the Host
parameter.
So basically Apache used as a proxy doesn't really "need" Host parameter
but it's to avoid bug when connecting, or example, to an Apache web
server which uses VirtualHost based certificates configurations with
HTTPS connections...
So yes it's only linked to the RFC.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/bug.php?id=44248
--
Edit this bug report at http://bugs.php.net/bug.php?id=44248&edit=1
