New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Failed to parse url" error when fetching a relative url #39
Comments
Ah, that's just a noisy parse function. Relative URLs are destined for the current origin, so XDomain will not hook them. The log is XDomain failing to find an origin in the URL and therefore ignores it, though normal XHR should still work. This should only appear when |
I can also reproduce it in the latest Firefox, if that helps your testing :) I managed to patch it quick-and-dirty using the code below, but I'm sure there's a more elegant way of fixing this.
|
Oh damn, just tested, its all browsers - requests to relative URLs fail, investigating now... |
fixed, thanks for the heads up, turns out i was missing 4 characters: |
Thanks for fixing the relative url issue so quickly! However, I still have an issue when using protocol-relative url's.
I'm using |
When I fetch a relative url, I get these errors on master:
LOG: xdomain (http://blaise.local:8000): failed to parse url: /some/relative/url/
I would expect relative url's (protocol-relative, host-relative) to work. Maybe patch
parseUrl
to prepend the master's protocol if the protocol is unspecified, and return the master's origin if no hostname is specified?Environment: Windows 7, IE9, Strict mode.
The text was updated successfully, but these errors were encountered: