[WebKit-devel] KIO::AccessManager

[Dawit A]

On Friday, June 18, 2010 12:37:37 Mehrdad Momeny wrote:
> Hi Urs and WebKit guys,
> 
> > On Thu, 17 Jun 2010 23:31:50 +0430, Mehrdad Momeny
> > 
> > <mehrdad.momeny at gmail.com> wrote:
> > > Hi,
> > > 
> > > Just want to use KIO::Integration::AccessManager in my app (Choqok) to
> > > pass it to a lib (QtOAuth) to
> > > use it instead of QNetworkAccessManager, to have KIO proxy settings and
> > 
> > ...
> > 
> > > But, It doesn't work well, i.e. I see results back from server (via
> > > Wireshark), but nothing happens
> > > in this class :-/ and it does not reply me anything.
> > > 
> > > It was work just one time, When Lukas Appelhans suggest me to remove
> > > ~/.kde/share/config/kio* and I
> > > did it.
> > > But after that, It doesn't work anymore :-(
> > > 
> > > Do you have any idea?
> > > This is really important for me! And I need it to work.
> > > 
> > > P.S. Just saw your name in class src as author :)
> > 
> > Hi Mehrdad
> > 
> > That sounds really strange to me.. Are you using it for "normal" HTTP
> > requests? Many parts of KDE are already using it and I'm not aware of
> > such issues.. Does QNetworkAccessManager work for you?
> 
> Yep, QNetworkAccessManager works fine for me,
> Hmm, It's an HTTP Get request to https://twitter.com/oauth/request_token
> through QtOAuth library (changed the Interface class to set my
> KIO::AccessManager to it.)

Well... sending the above request results in an invalid 401 response from the 
server (no Authorization header). Unfortunately, kio_http dealt with such 
responses by converting the response code from 401 to 200, which is what gets 
sent to KIO::Integration::AccessManager. I guess that is probably what is 
tripping up QtOAuth ???

Anyhow, the above problem has now been rectified in kio_http [1]. See if that 
resolves your problem. If it does not, open a bug report for it...

Regards,
Dawit A.

[1] http://websvn.kde.org/?view=revision&revision=1140136