You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.
In IRI spec domain is case insensitive and I'm wondering if in our case we should treat window.location.host as domain or as path?
Generally when getting files from package using XHR host (i.e. f15a6d20-cefa-13e5-1972-800e20d19a76), host functionally to me is more like domain (case sensitive) than path.
If we should treat host case sensitive then we should mention that in specification explicitly since as it is now I expect app scheme will work similarly to http, and it that case host should be case insensitive.
What do you think?
The text was updated successfully, but these errors were encountered:
What about all other normalizations that apply to regular IRIs, like character or percent-encoding ? Should we mention somewhere that app URI should comform to some specific URI standard, or is it too complicated?
On Thursday, July 18, 2013 at 3:03 PM, jmajnert wrote:
What about all other normalizations that apply to regular IRIs, like character or percent-encoding ? Should we mention somewhere that app URI should comform to some specific URI standard, or is it too complicated?
I want to layer the app:// URI spec on top of http://url.spec.whatwg.org. In theory, that should address all of the above.
In IRI spec domain is case insensitive and I'm wondering if in our case we should treat window.location.host as domain or as path?
Generally when getting files from package using XHR host (i.e. f15a6d20-cefa-13e5-1972-800e20d19a76), host functionally to me is more like domain (case sensitive) than path.
If we should treat host case sensitive then we should mention that in specification explicitly since as it is now I expect app scheme will work similarly to http, and it that case host should be case insensitive.
What do you think?
The text was updated successfully, but these errors were encountered: