Jan 14 16 3:34 pm
Jan 14 16 3:51 pm
Jan 14 16 4:01 pm
adrien wrote:Hi
which version of WinGate is this?
We had some old baked in rules relating to drive specifiers. I'm not sure if they are still there, but that error message rings a bell
Regards
Adrien
Jan 14 16 4:03 pm
Jan 14 16 4:06 pm
adrien wrote:Hi
I just checked the code history, that bug was introduced in 1999 for some unknown reason, and was fixed 24 June 2013, and the fix was first released in WinGate 8.0.0
So I guess you're running WinGate 7?
Regards
Adrien
Jan 14 16 4:27 pm
Jan 14 16 8:11 pm
Jan 15 16 7:36 am
MattP wrote:Hi,
The fix won't be migrated back to WinGate 7 so you will need to update to WinGate 8. If you would like to email sales@wingate.com we can let you know the cost to renew your version protection.
Matt
Jan 15 16 2:02 pm
Jan 15 16 3:44 pm
adrien wrote:Hi
sorry, there's no workaround, and unfortunately we aren't set up currently even to build the old WinGate 7 code tree any more so it's not just a simple matter of porting the fix back.
Windows 2000 was a great low-cost (in terms of resource usage) OS, and we only retired our last 2k machines about 12 months ago.
Adrien
Jan 17 16 12:56 pm
Jan 21 16 12:03 pm
Jan 21 16 3:37 pm
Jan 22 16 4:35 pm
adrien wrote:Hi
I resurrected our old build server, got the code to it and managed to get it to spit out a new build of WinGate 7.
It's untested, but should fix this problem for you. Only change since build 3535 was the fix for this issue.
http://www.wingate.com/downloads/latest/WinGate7.3.2.3536-USE.exe
Regards
Adrien
Jan 24 16 7:34 am
Jan 25 16 9:22 am
Jan 25 16 1:47 pm
Jan 27 16 1:07 pm
adrien wrote:I've been looking through this code more and more, and I'm struggling to see how this restriction can even be checked except for in the case of server requests.
Are you diverting port 80 to the proxy (e.g. to the proxy rather than via it) and then forward proxying it?
Adrien
Jan 27 16 4:06 pm
Jan 27 16 4:38 pm
Jan 28 16 4:25 pm