Earnie Boyd wrote:
> Quoting Greg Chicares <chicares@...>:
>> Could it be that the problem is in the automated MinGW installer,
>> or in its interaction with sf.net?
> So it is the SF UI redirect that causes the issue. I'm thinking they
> need to do an urlencode on the URI before passing to the API they're
> using but that is for SF to figure out.
I've just done some tests here with Firefox, IE, wget and the nsis
plugin. All appear to work for me with + characters in the URL, is this
behaving differently for different users?
There does appear to be some problem related to the /RESUME argument to
the inetc plugin. I'm getting occasional failures now if the argument is
a null string ( "" ) but everything seems to be fine if either the
argument is omitted or a non null string is supplied. I'll run a 5.1.3
release in an hour or two with an argument supplied - this supplies the
error message when the connection is interrupted or fails. I can add a
message to ask the user to check the IE proxty settings here as well.