Summary: | [GTK] comments link = page not found | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Tomas Rimkus <sandshrew> | ||||
Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | alp, sandshrew | ||||
Priority: | P2 | Keywords: | Curl, Gtk | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
URL: | http://rq.lt/2007/12/05/nusipiesiam/#comments | ||||||
Attachments: |
|
Description
Tomas Rimkus
2007-12-18 07:32:54 PST
Looks okay with a local debug build of WebKit r28828 with Safari 3.0.4 (523.12) on Mac OS X 10.4.11 (8S165). This is a bug in the curl http backend. It includes # and everything after # in the HTTP request. Created attachment 18541 [details]
Don't send the URL fragment part to the server
This fixes the known issues.
+ url = url.left(url.find('#'));
Hopefully someone who knows their HTTP can review this patch.
Is my fix robust ie. will the first '#' encountered always denote a URI fragment? Is there a better way to get the URL without the fragment using the KURL class rather than doing a string search?
Comment on attachment 18541 [details]
Don't send the URL fragment part to the server
Landed.
|