Re: function login call blew up

On Sat, 2002-05-18 at 20:48, John Berninger wrote:
>         For those of you interested in the technical details, the
> problem is definitely with the Current server; in early versions, Hunter
> exploited a ``feature'' of the up2date client which really wasn't
> supposed to be there by gzipping the package list and header
> information, and sending the gzipped data to the client when it was
> requested, in order to save disk space.  Well, with version 2.7.61 (the
> latest 7.[012] errata) and version 2.7.63 (stock 7.3), that feature was
> removed, so our server isn't talking to the clients in a way the clients
> understand anymore.  This was a relatively simple fix, it just took a
> bit to find and isolate it, and of course we've now got to go through
> the monkey business of creating and certifying new packages and such...

Recent up2date versions, including the one that ships with RHL7.3, use
the cgiwrap library to handle compressed payloads.  See
/usr/lib/python1.5/site-packages/cgiwrap.py  for which headers you need
to send to make it work correctly.  The Content-Transfer-Encoding header
should still work as before.  If you are having problems, then the issue
might be that up2date might not send an appropriate accept-encoding
header.

Thanks.
Peter