Fwd: [kde] https/konqueror (2)

George Staikos staikos at kde.org
Thu Feb 20 16:53:33 GMT 2003


On Thursday 20 February 2003 07:03, Waldo Bastian wrote:
> On Thursday 20 February 2003 09:50, thomas klein wrote:
> > On Wednesday 19 February 2003 18:53, George Staikos wrote:
> > > On Wednesday 19 February 2003 12:48, you wrote:
> > > > > Which version of Konqueror are we talking about? Persistent SSL
> > > >
> > > > connections
> > > >
> > > > > were disabled in KDE 3.0.x. With KDE 3.1.x they are supposed to
> > > > > work.
> > > > >
> > > > >  Not only that, but session ID caching was not implemented until
> > > > > this weekend.  It's in CVS now.
> > > >
> > > > I'm using kde 3.1 on a gentoo linux
> > >
> > >   Well as waldo said, http persistence should work, but ssl session
> > > reuse will not.  Which one do you see a problem with?
> >
> > I'm experiencing problems with ssl sessions.
> >
> > Konqueror have to take 20 or 30sec to load a page that galeon/mozilla
> > load in 2 or 3 (Not a troll), and some strange characters seems to
> > appears randomly before and after each objects
> > (like "
> > b3d
> > [Picture/object of the html page]
> > 0
> > ").
>
> That looks like something goes wrong with the chunked transfer-encoding.
>
> Maybe Konqy doesn't catch the header line that say that it is chunked. Then
> it will default to plain and it will use the close of the connection as
> end-of-data indication (and disable persistent connections). That takes a
> long time (e.g. 30 secs) because the server still thinks it has a
> persistent connection and doesn't close the connection after the transfer.
>
> Will need to see the headers as received by kio_http to see if that is the
> problem.

  Ok so to be clear, this is not ssl sessions, it's http.  SSL sessions 
related to the initial SSL handshake, key exchange, certificates, etc.  Those 
should be fine here, though not optimal.

-- 

George Staikos





More information about the kfm-devel mailing list