[webkit-dev] Possibly bogus FrameLoader::originalRequest data

tonikitoo (Antonio Gomes) tonikitoo at gmail.com
Fri Jul 17 09:28:22 PDT 2009


Hi. So I ran into this while developing a feature to qt webkit, but it
is possibly not a port specific issue, but webcore.

1) If i load an existent local page (through FrameLoader::load) that
redirects (e.g. file:///test1.html redirects to file:///test2.html) ,
i get

FrameLoader::originalRequest.url() to point to test1.html
FrameLoader::request.url() to point to test2.html

which seems to be the corrent behavior.

2) After that if i load another local but unexistent file (e.g.
file:///unexistent.html) i get:

FrameLoader::originalRequest.url() *still* points to test1.html
(previous loaded URL)
FrameLoader::request.url() points to file:///unexistent.html

whereas "originalRequest" pointing to a previous loaded url seems
clearly no right.  So, please correct if I am wrong, but
there should be a method resetind these data between this two load calls ?

also if I skip 1) and go to 2) straigh I get:

FrameLoader::originalRequest.url() as an empty URL
FrameLoader::request.url() to point to file:///unexistent.html

Is that expected ? What data should originalRequest hold in these cases ?

thanks

-- 
--Antonio Gomes


More information about the webkit-dev mailing list