Closed leon-thomm closed 1 year ago
I am realizing (or rather someone on the Rust Discord pointed out that) this is the numeric character reference of "/" in unicode which yields totally valid HTML. What is the reason for using NCRs instead of the characters themselves if Rust strings are already UTF-8?
This is just escaping HTML characters. Use {{ func() | safe }}
is the output is safe
I just started experimenting with tera, and I'm quite certain that this is a basic issue, but I couldn't find the answer in the guide and documentation. Consider the following code:
Expected output:
a/b
.Actual output:
a/b
.Notice
/
is the unicode hex-char code for/
. This does not happen when I remove the.html
fromtest.html
. Including<meta charset="utf-8">
in the parsed string doesn't help. Why is this happening?