What in the world happened to Wingate 2008??

[adrien]

just an update - still battling that recent issue with the Vista driver, we expect to put a RC into testing tomorrow with a fix for it.

[sduffey]

When will HTTP 1.1 be supported?

[adrien]

Hi

HTTP/1.1 is already mostly supported in 6.x, specifically chunking, and persistent connections, however there were some problems in the DNS resolver that prevented some names e.g. downloads.microsoft.com from resolving properly which may have created a similar problem for windows update.

We've tested windows update and it works fine through 6.5.

What error do you see running Windows Update through your existing WinGate?

Note also, if you have Kaspersky AV for WinGate installed, it removes range request headers - prevents clients from doing partial requests. This prevents the BITS service from working properly I believe. We need to prevent partial requests, else we can't scan the whole file.

so if this applies to you, you need to add the windows update sites as exclusions in Kaspersky AV for WinGate to stop it scanning them, and prevent blocking of range requests.

[sduffey]

We dont run Kaspersky. This is what is generated by a WSUS server trying to pull updates behind a Wingate 6.2.2 firewall.

Content file download failed. Reason: The server does not support the necessary HTTP protocol. Background Intelligent Transfer Service (BITS) requires that the server support the Range protocol header.

[adrien]

what about PureSight?

WinGate shouldn't be stripping those range tags out if there are no scanning plugins installed.

[sduffey]

We do run Pure Sight.

[logan]

We do run Pure Sight.

In that case you will need to manually classify the Windows update sites as "allowed" so that PureSight does not strip the range header from requests being made to those sites. Here are the steps to classify a site as "allowed" in PureSight.

1. In the GateKeeper, navigate to Plugins -> Puresight 2.0 for WinGate -> Manual classifications
2. At the bottom half of this configuration window, select "Any URL containing"
3. Enter "update.microsoft.com"
4. Select "Is to be classified as: Allow"
5. Click "Add"
6. Enter "download.microsoft.com"
7. Click "Add"
8. Enter "windowsupdate.com"
9. Click "Add"
10. Click "OK"

Your PureSight plugin will overlook microsoft updates after doing this. Let us know if you have any questions.