[opensuse-buildservice] special hack for handing off remote source requests to ajax server
Hi,
I identified a problem when accessing a remote OBS instance through a
squid proxy. The change
commit 5ed45e0096ff5051827c251c8fd384dd70debcbb
Author: Michael Schroeder
On Wed, Jan 11, 2012 at 03:24:46PM +0100, Robert Schiele wrote:
causes special handling if the user-agent string indicates that the other system is an OBS system as well, resulting in using chunked transfer encoding instead of having the content length. When this passes through the squid proxy the chunked transfer encoding is replaces by "normal" encoding but still the content-length not added.
Uh, I don't think this is legal. Either it's chunked or the content length must be known. Otherwise keepalive connections could not work.
The receiving OBS cannot deal with that situation.
Thus my question is, why was this special handling introduced and what would be the consequences if I disabled that? Is this just a performance downgrade or would that also have an impact on functionality.
Removing the commit would mean that (slow) downloads use a slot in the server for a long time. There's a only a fixed number available, thus you may run into a non-responsive server. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Uh, I don't think this is legal. Either it's chunked or the content length must be known. Otherwise keepalive connections could not work.
Well, I am not sure whether it is legal but in fact this is what squid apparently does when handling chunked transfer encoding data coming from the server. You are right that for sure keep-alive connections cannot handle that but squid handles that case by simply not using keep-alive then, even when the client asks for that. If someone knows a way to change this behavior in squid I would be happy to hear about it. I have full control over the squid configuration, thus if there is an option to change the behavior this would be another (and likely better) solution.
Removing the commit would mean that (slow) downloads use a slot in the server for a long time. There's a only a fixed number available, thus you may run into a non-responsive server.
Ok, thanks! Robert -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Michael Schroeder
-
Robert Schiele