ID: 46539 Updated by: sjo...@php.net Reported By: marques at displague dot com -Status: Open +Status: Bogus Bug Type: SOAP related Operating System: * PHP Version: 5.2.6 New Comment:
Thank you for your bug report. While the usage of digest authentication with HTTP/1.0 may very well be a bug, we have no interest in fixing it in the 5.2 branch. Fixing it would be much work and users can use PHP 5.3 instead if they experience this bug. The Host header is allowed in HTTP/1.0. The difference with HTTP/1.1 is that it is _required_ in HTTP/1.1. Previous Comments: ------------------------------------------------------------------------ [2009-07-27 12:24:25] alayn at irontec dot com Confirmed. My problem disappeared with 5.3 Sorry again ------------------------------------------------------------------------ [2009-07-23 13:52:08] alayn at irontec dot com Upssss... It seems like my bug is more related to: http://bugs.php.net/bug.php?id=47021 I will try 5.3 as soon as i have time for it. Sorry :S ------------------------------------------------------------------------ [2009-07-23 11:42:50] alayn at irontec dot com Using HTTP/1.0 for the WSDL request against a JAX-WS service, makes PHP freeze until timeout arrives, eventhought it gets the complete response. Not sure if this is a JAX-WS or PHP related issue, but I think it should be possible to resolve it by performing an HTTP/1.1 request... A related bug is reported at Java's bug system too: https://jax-ws.dev.java.net/issues/show_bug.cgi?id=257 It seems they resolved the issue with wget, but I still having the same problem from PHP 5.2.9 :( ------------------------------------------------------------------------ [2008-11-10 22:01:49] marques at displague dot com Description: ------------ When setting the SoapClient option 'authorization' to SOAP_AUTHENTICATION_DIGEST, the SoapClient connection should attempt to GET with HTTP/1.1 rather than HTTP/1.0 since digest is HTTP/1.1 specific. I also noticed that the HTTP/1.0 WSDL request issued by the SoapClient class used "Host:" lines. I may be wrong, but I thought that implied HTTP/1.1. (I don't see it in the HTTP/1.0 RFC). ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=46539&edit=1