Bug 142095 - Declaring a custom protocol for "http" causes navigation issues
Summary: Declaring a custom protocol for "http" causes navigation issues
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit2 (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-27 11:53 PST by redswill
Modified: 2015-02-27 22:40 PST (History)
0 users

See Also:

Attachments
Sample Project (45.95 KB, application/zip)
2015-02-27 11:53 PST, redswill 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description redswill 2015-02-27 11:53:33 PST 
Created attachment 247532 [details]
Sample Project

Registering a custom protocol for "http" causes navigation issues, even if the protocol does nothing (i.e. it always returns NO in canInitWithRequest:)

Steps to reproduce:
1. Open & run the attached sample project
2. Search Google for "getbootstrap"
3. Click on the result that takes you to getbootstrap.com
4. Notice how the page fails to load
5. Right click and show inspector, then go to errors
6. Notice how WebKit tries to load the getbootstrap.com resources from google.com

Basically, the custom protocol somehow causes WebKit to get confused about what its current URL is and how to resolve relative paths.