When parsing URLs, encode the character U+007F DELETE as "%7F". This improves readability, reduces spoofing risk, makes Chrome's behavior more consistent, interoperable with other browsers and compliant with the specification.


- U+7F is the only non-printable ASCII character that is not percent-encoded. One could rely on this for spoofing purpose. - The spec says it should be percent-encoded and WebKit and Gecko does it. - Blink already percent-encode U+7F in URLs in most cases, this change is about making it consistent by handling the same paths of non-special URLs (i.e. using schemes other than ftp, file, http, https, ws, wss) or URL fragments (i.e. #foo).


Specification link

Unknown standards status - check spec link for status

Status in Chromium


Enabled by default (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • Positive
  • Positive
  • Positive



Basic examples: * <a href="https://example.org/#&#x007F;">URL fragment</a> * <a href="https://example.org/&#x007F;">special URL path</a> * <a href="javascript:alert('&#x007F;')">non-special URL path</a> If you hover one link or follow it, the statusline and url bar should use %7F. Chrome does it for the first one but not for the others. Another example with JavaScript: (new URL('web+foo:\u007F').href should output "web+foo:%7F"

Search tags


Last updated on 2022-01-14