PhpDig.net - View Single Post

Charter · 08-01-2004, 01:48 AM

Hi. I don't believe this to be a PhpDig problem. I don't think that PhpDig is trying to reopen an already opened connection. I think that the server said that it was going to send a certain number of bytes, and then went ahead and sent a different number of bytes, ergo the message. The reason that this shows now is probably because PhpDig 1.8.3 sends and receives headers when retrieving page content, whereas PhpDig 1.8.0 didn't deal with headers when retrieving page content. Perhaps try PhpDig on something other than through a proxy server and see if the message goes away. If the server is in fact sending bad data, what is PhpDig to do?

08-01-2004, 01:48 AM	#4
Charter Head Mole Join Date: May 2003 Posts: 2,539	Hi. I don't believe this to be a PhpDig problem. I don't think that PhpDig is trying to reopen an already opened connection. I think that the server said that it was going to send a certain number of bytes, and then went ahead and sent a different number of bytes, ergo the message. The reason that this shows now is probably because PhpDig 1.8.3 sends and receives headers when retrieving page content, whereas PhpDig 1.8.0 didn't deal with headers when retrieving page content. Perhaps try PhpDig on something other than through a proxy server and see if the message goes away. If the server is in fact sending bad data, what is PhpDig to do? __________________ Responses are offered on a voluntary if/as time is available basis, no guarantees. Double posting or bumping threads will not get your question answered any faster. No support via PM or email, responses not guaranteed. Thank you for your comprehension.