Eliezer and Amos
I filed Bug 4012 in squid bugzilla - reverse SSL proxy cannot handle file uploads to backend parent SSL servers today Attached to the Bug are the config file and log files and tcpdump txt files for client side and sever side connections in a reserve proxy set up looks like squid is sending tcp resets to stop the unknown size file transfer in ssl reverse proxy? Could you please look at the issue? -----Original Message----- From: Eliezer Croitoru <elie...@ngtech.co.il> To: squid-users@squid-cache.org Subject: Re: [squid-users] Squid 3.3 Reverse Proxy Mode - 502 Errors when uploading files larger than 6MB Date: Tue, 26 Nov 2013 05:31:16 +0200 Hey Madhav, I will try to test it later with 3.3.10 to make sure I get the same issue in a reverse proxy with a http cache_peer. To test a SSL cache_peer for me it will take a bit longer. If you can file a bug at the project Bugzilla it would help to keep track about this issue at: http://bugs.squid-cache.org/ Since we have two different "cases" in hand which is "reverse vs forward" and "http vs https" I will later-on add a list of tests to the Bugzilla to minimize the issue into a very specific case which then can be analyzed and solved. The subject of the bug can be "https big POST request failing in the middle" or any similar one. If you can add also to the frontend a http port just to check if in a case of http frontend and http backhand is similar it will might help more. You can use it on port 10800 if you want since squid doesn't care about the port in this specific case. Regards, Eliezer On 23/11/13 06:36, Madhav V Diwan wrote: > Eliezer > > I just now tried a connection with the cache_peer set to port 80 > without SSL , i left the frontend ssl > > same result.. tiny file makes it through , larger files do not. > > Madhav
