-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
On 4/27/12 3:55 AM, André Warnier wrote: > And the main issue is that, while it is uploading the data, the > browser isn't reading anything from the webserver. Yeah, I'm fairly sure that this is the problem. > Sending a response to the browser including a "Connection: close" > header, just tells the browser that it will not be able to send > *its next request* on the same HTTP/TCP connection, and that it > will have to build a new connection. But it doesn't impact the > current request/response cycle. Yes, I'm well aware of that. > If this thing of stopping the browser waisting its time is really > important in your case, then on the base of the above, one could > imagine a solution, based on for example a specialised browser > "applet" which would send the file-to-upload using a separate HTTP > request including an "Expect" header (see section 8.2.3), then > waiting for the server to answer with a "100 Continue" response > before sending the body. Yeah, it's too bad I can't force the client to act like that. If I could, I would object to the Content-Length immediately and then the bytes would never even have to be sent. Thanks, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+a54UACgkQ9CaO5/Lv0PBehgCfY6GhIdv6hwCLpYiBk8I47+CQ XRkAoJzGRq075TdrNZ30zr9VyjFvcPS8 =X2KB -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
