Enable autoescape in jinja templates #195
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prior to this change, special HTML characters in metadata (e.g. titles) were not being escaped.
saimn
added a commit
that referenced
this pull request
Feb 29, 2016
Enable autoescape in jinja templates
|
Thanks ! |
kontza
pushed a commit
to kontza/sigal
that referenced
this pull request
Aug 28, 2020
Enable autoescape in jinja templates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Special HTML characters in album and media metatdata were not being escaped in the generated HTML pages. So if a album title contained a
<, for example, there was trouble.This pull request turns on jinja2’s autoescape feature, which solves the problem.