From 68fb0071f157c91fc8e1a5123f9fcf0fbfd40b31 Mon Sep 17 00:00:00 2001 From: Anthony Fok Date: Tue, 20 Jan 2015 00:24:47 -0700 Subject: [PATCH] [Docs] Incorporate some great ideas by @mohae into the `safeUrl` docs E.g. how `#ZgotomlZ` is used to "defang" the URL --- content/templates/functions.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/templates/functions.md b/content/templates/functions.md index 98785a53e..89c866951 100644 --- a/content/templates/functions.md +++ b/content/templates/functions.md @@ -326,9 +326,10 @@ filtered out since they are a frequently exploited injection vector. [RFC 3986]: http://tools.ietf.org/html/rfc3986 Without `safeUrl`, only the URI schemes `http:`, `https:` and `mailto:` -are considered safe. All other URI schemes, e.g. `irc:` and -`javascript:`, get filtered and replaced with the `ZgotmplZ` unsafe -content indicator. +are considered safe by Go. If any other URI schemes, e.g. `irc:` and +`javascript:`, are detected, the whole URL would be replaced with +`#ZgotmplZ`. This is to "defang" any potential attack in the URL, +rendering it useless. Example: Given a site-wide `config.toml` that contains this menu entry: