On Tue, 2005-11-29 at 10:47 -0500, William Warren wrote:
> i would rather not simply circumvent this isue...i would rather it be
> fixed. Like i psoted to naother person..squid is a great proxy..that is
> unless it is one that now sucks.
>
Yum is not maintained by CentOS ... it is something that we use from
somewhere else. We use what they produce, so there is no timetable.
It isn't proxy servers in general, just some implementations that don't
work well.
I am using squid on my network and I get updates through it for 10
machines with no problems.
A transparent proxy is one where ports are routed behind the scenes and
there is no setup file.
Using an FTP server is best in these situations.
> Karanbir Singh wrote:
> > William Warren wrote:
> >
> >> Is there a timetable to fix the yum/http proxy incompatibility? i
> >> find it interesting this has not been addressed yet.
> >>
> >>
> >>> 3. Another common problem is transparent proxy servers and yum. HTTP
> >>> mirrors and yum don't work really well via transparent proxy servers, so
> >>> if you are using one, your best bet is to pick an FTP mirror from our
> >>> public external server list (see mirror link above) instead of
> >>> mirror.centos.org.
> >
> >
> > why not ask the guys who built the proxy, thats where the breakage is
> > mostly.
> >
> > Also, you have the option of going to a ftp mirror, and circumvent this
> > issue.
> >
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.centos.org/pipermail/centos/attachments/20051129/28823678/attachment.bin
