Done: http://bugs.squid-cache.org/show_bug.cgi?id=4048
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-3-4-Zero-Sized-Reply-for-HTTP-POST-tp4665601p4665666.html
Sent from the Squid - Users mailing list archive at Nabble.com.
Can you please file a bug report on the issue?
There is maybe a way to solve it if will be needed in the future and
also it has a significant effect on errors.
http://bugs.squid-cache.org/
If it's too hard let me now via email and I will fill the blanks about
the server version and settings f
I managed to solve the problem. It seems that this problem only occurs when
using TLS 1.0 which was the highest allowed by the backend servers by
default. Enabling TLS 1.2 on the servers and telling squid to use this fixed
the issue.
Hopefully this will help someone else experiencing the same issu
On 04/16/2014 01:36 PM, tomsl wrote:
Additional information: This only happens when squid uses HTTPS to connect to
the origin server. HTTP appears to work fine.
This issue was as a topic before but never really had the chance of
verifying the issue fully.
Can you file a bug in the bugzilla?
ht
Additional information: This only happens when squid uses HTTPS to connect to
the origin server. HTTP appears to work fine.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-3-4-Zero-Sized-Reply-for-HTTP-POST-tp4665601p4665609.html
Sent from the Squid -
I turned on some debug logging and everything appears to work fine until the
file upload completes and it then just hangs for a few minutes. I then get
this:
2014/04/15 15:45:14.107 kid1| Server.cc(361) sentRequestBody:
sentRequestBody: FD 12: size 4095: errflag 0.
2014/04/15 15:50:13.072 kid1| A
