Re: [squid-users] squid 3.2 and POST

Hi.

On 16.07.2013 10:30, Amos Jeffries wrote:
>
> Nasty as they are, the above are the perfectly normal "working" NTLM
> behaviour. If your traces are showing something else going on *by
> Squid* then you have a bug. We have indeed found a few such bugs in
> Squid NTLM and persistence handling, once you have confirmed that it
> is a bug and not just one of the above "working" NTLM problems please
> repeat the test using the latest 3.3 release and if possible the
> latest 3.HEAD daily bundle to see if it is one we found and fixed
> already. http://wiki.squid-cache.org/SquidFaq/BugReporting has more on
> the process of reporting.
>
> NP: There was one bug fixed in 3.3.1 related to HTTP/1.1 keep-alive
> which was showing up in some NTLM clients and is possibly seen in 3.2
> still. The Squid-3.3 patch can be found here
> http://www.squid-cache.org/Versions/v3/3.3/changesets/squid-3-10728.patch
> although the preferred action is of course to upgrade to latest 3.3.
> Squid is on a release-often cycle now so the 3.2->3.3 changes are
> quite small compared to previous version differences (much safer for
> production servers to do than ever before).
>
>
> PS. I expect to have some time in the next few weeks and will be
> looking into similar issues with another client if you need a
> developer to take a closer look at fixing it and can pay for
> development support time. Contact me privately about support contracts
> please. Of course with any luck it will be that bug 2936 or another
> unidentified issue fixed in 3.3.
>
>
Thanks a lot for a detailed explanation, Amos ! And yeah, I tried the
new 3.3.x branch and it's working for me there.

Thanks again.
Eugene.
Received on Tue Jul 16 2013 - 08:27:31 MDT