Re: sockets - fine tunning
| From: | Raditha Dissanayake | Date: | Tue, 28 Oct 2003 13:30:44 +0000 |
| Subject: | Re: sockets - fine tunning | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-167868@lists.php.net to get a copy of this message | ||
Hi,
I think curt is right about transfer encoding being a problem, however i feel it may not be 'the' problem. This timing issue looks like you are running into a 'blocking' kind of situation. Cosmin, Have you tried the 'Connection: close' header?
Getting back to transfer encoding you might want to look at the RFC - http://www.w3.org/Protocols/rfc2616/rfc2616.html
where they explain how it's to be handled.
all the best
Curt Zirzow wrote:
* Thus wrote Cosmin (cosminb@as.ro):-- Raditha Dissanayake. ------------------------------------------------------------------------ http://www.radinks.com/sftp/ | http://www.raditha/megaupload/ Lean and mean Secure FTP applet with | Mega Upload - PHP file uploader Graphical User Inteface. Just 150 KB | with progress bar.On Sun, 2003-10-26 at 15:30, Raditha Dissanayake wrote:This is probably the problem. If you inspect your data, you'll notice that it has extra characters in it right now. You can change your protocol version to HTTP/1.0 or send a header to tell the server you don't want chuncked (don't know that off hand). Curtare you getting any 1xx status codes from the web server?here are the full headers: Transfer-Encoding: chunked