If you have an <a> element with attribute href set to an URI without the //, weird things happen…
- Same as base URI's scheme (which is HTTPS).
- Parsed as scheme followed by relative path component.
- Behavior is described in RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax page 32, which itself refers to behavior mentioned in RFC 1630: URIs in WWW page 10.
- Scheme is different from base URI's scheme.
- Parsed as scheme followed by hostname.
| user agent | handles (1) | handles (2) | works in input bar/from command line |
|---|---|---|---|
| Firefox | ✓ | ✓ | ✓ |
| Chrome | ✓ | ✓ | ✓ |
| Opera | ✓ | ✓ | ✓ |
| Safari | ✓ | ✓ | ✓ |
| XXXTerm | ✓ | ✓ | ✗ |
| IE | ✓ | ✗ | ✓ |
wget -r |
✗ | ✗ | ✗ |
| lynx | ✗ | ✗ | ✗ |
curl |
N/A | N/A | ✗ |
Don't mind this. I prefer writing things down to bookmarks.
- https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#Specifications
- http://www.w3.org/TR/html401/struct/links.html#edef-BASE
- http://www.ietf.org/rfc/rfc2396.txt
- http://www.w3.org/TR/html5/text-level-semantics.html#the-a-element
- https://en.wikipedia.org/wiki/Backus%E2%80%93Naur_Form
- https://en.wikipedia.org/wiki/URI_scheme#Generic_syntax