PATCH: Better cross-domain cookie detection [BR 66090]

Waldo Bastian bastian at kde.org
Tue Dec 2 14:38:50 GMT 2003


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

On Tue December 02 2003 15:26, Dawit A. wrote:
> > The request is usually actually started by doing:
> > 	emit d->m_extension->openURLRequest
> >
> > Then konqueror starts the job, looks at the mimetype that comes back and
> > decides to hand the URL over to the khtml_part//openURL which then starts
> > a new job which will get the original slave+response handed over by the
> > scheduler.
>
> Ahhh... Good thing you mentioned that. I found the problem. It is
> konqueror's attempt to detect the mimetype that was causing this issue. The
> "cross-domain" meta-data needs to be added to BrowserRun::scanFile and
> possibly to KRun::scanFile as well. That fixes my problem.

But in this case cross-domain is set to the url that is requested, no? Does it 
make sense to set it at all in such case?

And can you change sourceURL() to toplevelURL() as previously agreed?

Cheers,
Waldo
- -- 
bastian at kde.org -=|[ SUSE, The Linux Desktop Experts ]|=- bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/zKP6N4pvrENfboIRAj5XAJ4hmLTu/VMSKWKYFQjcj9hhcO5//ACcCEiz
JgjoQWAvDQQ3kIEHxdkP7u4=
=HwTE
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list