|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Let me try to disable my workaround again and check if Chrome attempts charset autodetection (which would be a violation of the HTTP standard, but whatever, sometimes software sacrifices standards for better user experience).
checks
Nope, there's no autodetection. I see gibberish.
Why not serve the files from the workspace using the locale charset, which Jenkin already knows?
/systemInfo: