Problem:
Asset library web pages send no Content-type header
Effects:
Web browsers may fall back to display pages as text/plain or ask user what to do (download, display as text/plain, ...).
The authors seem to have worked on this problem by adding <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> to the reset_password_email.html template.
Problem: Asset library web pages send no Content-type header
Effects: Web browsers may fall back to display pages as text/plain or ask user what to do (download, display as text/plain, ...). The authors seem to have worked on this problem by adding
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
to the reset_password_email.html template.Example response:
Solution: Let the middleware add a Content-type header matching the MIME-type of the content to display.