>
> On Sun, 15 Feb 2004 bovineone_at_users.sourceforge.net wrote:
>
> > I can confirm that the new cURL behavior of checking for 0x01 no
> > longer works in my development environment, but patching the check
> > back to 0x05 fixes the problem.
>
> Thank you for your patience and your informative reply and
> responses in the bug tracker.
>
> I take it my commit that now brings back the check for 5 thus
> makes the CVS version of curl once again behave correctly?
>

Current CVS checkout has been verified to bring back the check for 0x05, and
we are able to confirm that it now works against our Windows NEC SOCKS5
proxy without any additional patches.
Received on 2004-02-25