[JIRA] (JENKINS-40043) Allow custom values for Content-Type Header in Pipelines
Title: Message Title Stephan Burkard created an issue Jenkins / JENKINS-40043 Allow custom values for Content-Type Header in Pipelines Issue Type: Improvement Assignee: Janario Oliveira Components: http-request-plugin Created: 2016/Nov/25 4:06 PM Environment: Jenkins 2.7.3, http-request 1.8.12 Labels: http Priority: Major Reporter: Stephan Burkard When I use the http-request plugin in a pipeline, the page https://jenkins.io/doc/pipeline/steps/http_request/ lists the possible values for the optional headers contentType and acceptType. The fixed list of (very few) types is a killer for the plugin usage, because there is (for example) no value for XML data (text/xml or application/xml). In addition the content-type cannot contain any charset information when it contains only the mime-type. I would like to set a content-type like text/xml; charset=UTF-8 which is currently not possible. When I do not set the contentType parameter, the request arrives at the server with contentType text/plain; charset=ISO-8859-1. Therefore I cannot use the http-request plugin and have to use wget via shell instead. To remove such limitations and increase plugin usage, it would probably be better to allow any string as contentType. There are so many mime-types and charsets available, I don't think this can be limited to an Enumeration.
[JIRA] (JENKINS-40043) Allow custom values for Content-Type Header in Pipelines
Title: Message Title
Stephan Burkard updated an issue
Jenkins / JENKINS-40043
Allow custom values for Content-Type Header in Pipelines
I changed the ticket text and priority since I can set a custom Content-Type via the customHeaders parameter.
Change By:
Stephan Burkard
Priority:
Major Minor
When I use the http-request plugin in a pipeline, the page https://jenkins.io/doc/pipeline/steps/http_request/ lists the possible values for the optional headers {{contentType}} and {{acceptType}}. The *fixed list of (very few) types is a killer for the plugin usage not very helpful *, because there is (for example) no value for XML data ({{text/xml}} or {{application/xml}}). In addition the content-type *cannot contain any charset information* when it contains only the mime-type. I would like to set a content-type like {{text/xml; charset=UTF-8}} which is currently not only possible . When I do not set by using the {{ contentType customHeaders }} parameter , the request arrives at the server with contentType {{text/plain; charset=ISO-8859-1}} . *Therefore I cannot use the http-request plugin and have to use wget via shell instead.* To remove such limitations and increase plugin usage, it It would probably be better to allow any string as {{contentType}}. There are so many mime-types and charsets available, I don't think this can be limited to an Enumeration.
Add Comment
[JIRA] (JENKINS-40043) Allow custom values for Content-Type Header in Pipelines
Title: Message Title Janario Oliveira commented on JENKINS-40043 Re: Allow custom values for Content-Type Header in Pipelines I plan to deprecate 'acceptType', 'contentType' in favor to use headers. It's bad to have 2 configuration that do the same, and one of it very limited. Also it could generate duplicated headers from both. But I plan to do it keeping compatibility. 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-40043) Allow custom values for Content-Type Header in Pipelines
Title: Message Title Janario Oliveira closed an issue as Won't Do Jenkins / JENKINS-40043 Allow custom values for Content-Type Header in Pipelines 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.
