resolves #48: custom css ineffectual behind reverse proxy
Caddy (and probably other webservers) add a Content-Type header when one was not supplied by the application backend. Under Chromium, the css file is not interpreted if the webserver delivers it with Content-Type: text/plain, althugh it does work if no Content-Type header is set. To prevent the frontend proxy from adding the wrong header, set it correctly in the first placepull/53/head
parent
083f136186
commit
ce81be85c7
Loading…
Reference in new issue