Updating Centos Server using Yum from behind Wingate 6

[cyberforester]

I am trying to do a yum update of a Centos server from behind our WIngate proxy. I keep getting an error [Errno -1] Header is not complete

I have determined from the Linux lists that this is due to a problem with the Proxy server and fragmentation or mistagging of headers. Yum uses http 1.1


here's what i have from the list:

"It's probably a proxy somewhere between you and the repository. You may not think that a proxy is in the way even though it really is.
You can try doing a "trace" with this command:
echo -e "TRACE / HTTP/1.1\nHost: yum-server.example.com\n\n" | nc yum-server.example.com 80
Which should give you some more information about the network between you and the repository. Also, be sure to replace yum-server.example.com with whatever your yum repository server is.
Another diagnosis step is to get the box off of that network (not always entirely possible, but port forwarding, VPN, or dialup can simulate the experience) and see if you still have the problem.
The solutions to this problem are:
1. Get your proxy software/firmware updated so that it properly implements HTTP 1.1
2. Use an FTP repository, where byte ranges are more commonly supported by the proxy
3. Create a local mirror with rsync and then point your yum.conf to that local mirror
4. Don't use yum"

I don't want to do 2, 3, or 4. I want to do 1 above. please help.

[rboynton]

Are you, by chance, using either (or both) KAV or Puresight plugins?

[logan]

WinGate 6.x doesn't properly implement HTTP 1.1. The WWW Proxy has been rewritten from the ground up for our next major release of WinGate and will include full HTTP 1.1 support.

Is Yum able to use an alternative proxy service for updates, like the SOCKS proxy service for instance.

[cyberforester]

So this is still causing me grief.

We are using PureSight, but I don't think that is the problem - at least not from what I have read.

I have tried using Socks, but that has not helped at all.

[jamescap]

We are using PureSight, but I don't think that is the problem

Well, it might be better to ‘know’ than ‘think’; have you considered either disabling PureSight for the sake of testing, or create a new WWW Proxy on a different port without PureSight attached to it, and try to update Yum through that?

I understand that:

I don't want to do 2, 3, or 4. I want to do 1 above

But for the sake of trying to help, have you considered trying a TCP Mapping?

For example, right click an existing proxy in WinGate and create a new TCP Mapping.
Select a unique port number e.g. 88, that this service will listen on.
For the mapping address enter in the address and port number for this repository.
Then enter Yum's setup and configure it so to do a direct connection to WinGate servers IP Address on Port 88, then the TCP Mapping will just relay it to the repository.