I am experiencing a problem with my API integration with Jenkins, when authentication is enabled. In short, all successfully authenticated requests come back as JSON, but invalid credentials return a 401 (great) but in an HTML format (not so great).
For example: I can probably code around it, but I really don't want to cope with HTML when I am expecting JSON, ideally. Feels like a bug. If so, should I be submitting it to a bug tracking system? Michael -- View this message in context: http://jenkins.361315.n4.nabble.com/401-messages-return-as-HTML-when-JSON-requested-tp4667482.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- 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/groups/opt_out.
