3 ms·
It's not supported in any browser, so good luck using it on the web. Even more, the semantics for such a URL as defined by RFC6784 means that common HTTP featur
by tsimionescu 5y ago
It's not supported in any browser, so good luck using it on the web. Even more, the semantics for such a URL as defined by RFC6784 means that common HTTP features like redirects can't work: client sends a request to http://[fe80::6%7] http://[fe80::6%7], the User Agent sends a request to server with "Host: http://[fe80::6] http://[fe80::6]", and receieves a 302 response with "Location: https://[fe80::6] https://[fe80::6]" . What can client do next?