segfault in http kioslave

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 17 September 2002 07:20 pm, Dawit A. wrote:
> On Tuesday 17 September 2002 02:03, Waldo Bastian wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Monday 16 September 2002 10:40 pm, Dawit A. wrote:
> > > I know why this bug occurs.  We default to the strongest possible
> > > authentication by default which in retrospect is not a good idea since
> > > more information is needed to compute digest authentication.  It would
> > > have worked without a problem if we defaulted to "Basic".  Will fix
> > > this issue. BTW, how did you register the password before hand ?  If it
> > > was done through the interface this should not have happened.
> >
> > We shouldn't default to anything in that case IMO and just make the
> > server roundtrip.
>
> Huh ? Come again... This will break everything and you will get bug reports
> that kio_http floods the servers when attempting to get a page, i.e.
> besides the kio_http is slow reports.  I think everybody completely
> misunderstands why and how authentication header is pre-emptively added. 

You miss the point.

Once we have received a response from the webserver we know whether the 
webserver wants Basic or Digest. We store that information in digestInfo. All 
further connections will preemptively send authentication using this very 
method.

However, if we have never received either a Basic or a Digest response 
(digestInfo is empty) we don't know what to sent, and in that case we 
shouldn't send anything but just wait for the first response from the server.

Cheers,
Waldo
- -- 
bastian at kde.org  |   SuSE Labs KDE Developer  |  bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9iAzzN4pvrENfboIRAt04AKCnxa4w1khUQv/jAOG0p18xd5UbCACeJ1ko
WmpKlUBmmbPMBHnvwoxTUJ0=
=d/hU
-----END PGP SIGNATURE-----