-
Bug
-
Resolution: Not a bug
-
Medium (View bug fix roadmap)
-
None
-
3.7 Beta 1
-
None
-
.NET 1.1 WebService Client
-
3.07
-
Header from WebService call to http://jira.atlassian.com/rpc/soap/jirasoapservice-v2 responds with
<HTTPHeaders>
<date>Sun, 12 Nov 2006 02:19:07 GMT</date>
<server>Apache/2.0.52 (Red Hat)</server>
<keep-alive>timeout=15, max=100</keep-alive>
<connection>Keep-Alive</connection>
<transfer-encoding>chunked</transfer-encoding>
<content-type>text/plain; charset=UTF-8</content-type>
</HTTPHeaders>
This causes a soap client to complain that the content type is supposed to be text/xml
Seems that this is the same issue as JRA-10743
- relates to
-
JRASERVER-10743 Visual studio 2005 c# client breaks on calling jira soap service
-
- Closed
-
[JRASERVER-11515] SOAP Response Content Type is 'text/plain' instead of 'text/xml'
Minimum Version | New: 3.07 |
Component/s | Original: Ecosystem - SOAP & XML-RPC API [Obsolete] [ 10480 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2839166 ] | New: JAC Bug Workflow v3 [ 2911581 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2569241 ] | New: JAC Bug Workflow v2 [ 2839166 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1535518 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2569241 ] |
Labels | New: affects-server |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 674462 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1535518 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 656067 ] | New: JIRA Bug Workflow w Kanban v6 [ 674462 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 265618 ] | New: JIRA Bug Workflow w Kanban v6 [ 656067 ] |
Workflow | Original: JIRA Bug Workflow + Quality v4 [ 252215 ] | New: JIRA Bug Workflow w Kanban v5 [ 265618 ] |