[JIRA] (JENKINS-62122) REST: Broken encoding results in 500 without a Reason Phrase given

[julian.schill...@continentale.de (JIRA)]

Title: Message Title

Julian Schilling created an issue   Jenkins / JENKINS-62122 REST: Broken encoding results in 500 without a Reason Phrase given Issue Type: Improvement Assignee: Unassigned Components: core Created: 2020-04-30 11:11 Priority: Minor Reporter: Julian Schilling When attempting to upload a config.xml with a broken encoding (for example, you attempted to upload ö which happens when an UTF-8 "ö" is interpreted as ISO 8859-1), Jenkins refuses to accept that encoding and answers with a 500. This is fine. However, it would make it easier to debug things if any kind of reason phrase would be given, if only "Illegal characters in config.xml" or alike. Finding this error can otherwise be tedious, especially if this happens in a largely automated environment. Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206034.1588245091000.19909.1588245120245%40Atlassian.JIRA.