|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The problem is that Jenkins just has no way to determine what charset any given file is. Serving any arbitrary file created by user-controlled means cannot work AFAICT, so I guess this is something we need to live with.
When there's no explicit encoding, client may do some autodetection though, so the current state seems to be the best possible.
Given these limitations, I'm tempted to resolve as Won't Fix. Any opposing views?