[JIRA] (JENKINS-40873) Recent change to content-type support breaks default text/plain
Title: Message Title Janario Oliveira closed an issue as Cannot Reproduce Jenkins / JENKINS-40873 Recent change to content-type support breaks default text/plain Change By: Janario Oliveira Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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.
[JIRA] (JENKINS-40873) Recent change to content-type support breaks default text/plain
Title: Message Title Janario Oliveira commented on JENKINS-40873 Re: Recent change to content-type support breaks default text/plain I've tried with version 1.8.13, 1.8.12 and 1.8.11 against requestb.in and when the value is NOT_SET it doesn't send the header. Do you have any other configuration that could cause this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
[JIRA] (JENKINS-40873) Recent change to content-type support breaks default text/plain
Title: Message Title Richard Lee created an issue Jenkins / JENKINS-40873 Recent change to content-type support breaks default text/plain Issue Type: New Feature Assignee: Janario Oliveira Components: http-request-plugin Created: 2017/Jan/06 11:52 PM Priority: Minor Reporter: Richard Lee I believe that this change https://github.com/jenkinsci/http-request-plugin/commit/8620e917855676506c85d2882a53192191bce6c2 broke support for not setting the contentType in an httpRequest. Previously, it would not pass any contentType parameter to StringEntity, which meant to use 'text/plain'. Now, I believe if you don't explicitly set the contentType, it passes the value of NOT_SET (which is "") to StringEntity, which then perhaps does something weird and causes requests to fail. I have working code that, at some version prior to 1.8.13, worked, and with 1.8.13 does not work. Adding an explicit contentType: 'TEXT_PLAIN' to my httpRequest command causes it to work again. Add Comment
