Thu, 09 Sep 2004
According to Derek, hrefs such as
<a href="https:/path"> should be valid and link to the same site using
https as the protocol.
This doesn't work in Mozilla, which converts such links to https://path/, nor in links which interprets it as
http://domain.tld/https:/path.
Interestingly, it does work in Mozilla if the link is the same protocol as
you're currently using.
If it worked, it would make web development easier. You wouldn't have to
use tokens in html templates for the server name to avoid hard coding in
the production server's domain. I'm sure there are other's who've used
output buffering hacks to
rewrite relative links.
So, what's the deal? Are all web browsers broken?
tech | Permanent Link
