Very interesting. The system is configured to hit our proxy server which determines that the web site is internal. Once it determines the site is internal it's "supposed to" just do the connection internally. If I turn of http_proxy from my environment variable, the http connection works also. -----Original Message----- From: yum-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:yum-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Michael Stenner Sent: Tuesday, November 14, 2006 1:44 PM To: Yellowdog Updater, Modified Subject: Re: Http errors connection to repository On Tue, Nov 14, 2006 at 01:15:30PM -0600, Stephens, Bill {PBSG} wrote: > Baseurl(s) for repo: ['http://devlinux.pbsg.pvt/sles10/'] > http://devlinux.pbsg.pvt/sles10/repodata/repomd.xml: [Errno 14] HTTP > Error 502: Date: Tue, 14 Nov 2006 19:12:59 GMT > Content-Length: 1116 > Content-Type: text/html > Server: NetCache appliance (NetApp/5.6.2D24) > Connection: close Thank you for providing headers. That's very helpful. Indeed, you DO have a gateway/proxy in the loop, and THAT is what's generating this error. Now, we don't know why yet, but obviously yum/urlgrabber are doing something differently from wget. I suggest looking at your server logs (on both server and proxy if you can) and also doing packet sniffing (I like ethereal) wherever possible. I'd like to see what's happening at the client end, but the server end would be useful, too. -Michael -- Michael D. Stenner mstenner@xxxxxxxxxxxxxxx ECE Department and Optical Sciences Center 520-626-1619 University of Arizona ECE 524G _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum
