#41983 [Asn->Csd]: Error Fetching http headers

ID: 41983 Updated by: dmitry@php.net Reported By: ipso at snappymail dot ca -Status: Assigned +Status: Closed Bug Type: SOAP related Operating System: Linux PHP Version: 5.2.3 Assigned To: dmitry New Comment: This bug has been fixed in CVS. 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: ------------------------------------------------------------------------ [2007-07-21 17:22:21] ipso at snappymail dot ca Sorry, here is the file and line that needs changing: ext/soap/php_http.c:1298 ------------------------------------------------------------------------ [2007-07-21 17:20:16] ipso at snappymail dot ca I had someone look into this for me, apparently the device isn't sending the "\r\n" at the end of the header, but only "\n". So instead of: if (strcmp(headerbuf, "\r\n") == 0) { Use: if (strcmp(headerbuf, "\r\n") == 0 || strcmp(headerbuf, "\n") == 0) { ------------------------------------------------------------------------ [2007-07-19 16:27:17] ipso at snappymail dot ca Just wanted to follow-up and make sure you got the email okay and have all the data you need to help track down the issue? Thanks for looking into this. ------------------------------------------------------------------------ [2007-07-13 15:40:56] ipso at snappymail dot ca I emailed a TCP dump of the SOAP request/response to: dmitry@php.net ------------------------------------------------------------------------ [2007-07-13 08:34:27] dmitry@php.net It seems like some kind of incompatibility between ext/soap and your soap or HTTP server. To fix the problem I need capture of HTTP response in binary form (including all special chars). Or give me a real PHP code that access buggy SOAP server so I'll able to reproduce it myself. ------------------------------------------------------------------------ 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/41983 -- Edit this bug report at http://bugs.php.net/?id=41983&edit=1