[jira] Created: (MUSE-275) MiniServlet uses incorrect SOAP 1.1 content type

MiniServlet uses incorrect SOAP 1.1 content type
------------------------------------------------

                 Key: MUSE-275
                 URL: https://issues.apache.org/jira/browse/MUSE-275
             Project: Muse
          Issue Type: Bug
    Affects Versions: 2.2.0
         Environment: Windows XP, OSGi
            Reporter: Bert Lamb
            Assignee: Dan Jemiolo
             Fix For: 2.3.0


I have been working through creating client for a service I am exposing using the Muse mini platform.  My client complained about "Transport level information does not match with SOAP Message namespace URI" when parsing the responses from Muse.  I used TCPMon and sure enough Muse was setting the content type of the responses to "text/xml; charset=Cp1252" while the SOAP Envelope namespace was being set as xmlns:soap="http://www.w3.org/2003/05/soap-envelope"

This is a mismatch, SOAP 1.2 requires the content type to be "application/soap+xml"
http://hadleynet.org/marc/whatsnew.html#S3.7.1

It looks like my client library (using axis2) also requires the content encoding to be UTF-8.  So the Content-Type header on the responses from Muse should be:

Content-Type: application/soap+xml; charset=UTF-8

Looking at org.apache.muse.core.platform.mini.MiniServlet it looks like responses are currently hard coded to be "text/xml" which does not appear to be correct.

I'm not sure if it is the best long term fix, but I will attach a patch that fixes this line to hard code to application/soap+xml instead.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@...
For additional commands, e-mail: muse-dev-help@...

     [ https://issues.apache.org/jira/browse/MUSE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bert Lamb updated MUSE-275:
---------------------------

    Attachment: content-type-fix.patch

Patch to change content type set for responses in MiniServlet from "text/xml" to "application/soap+xml" to be compliant with SOAP 1.2

> MiniServlet uses incorrect SOAP 1.1 content type
> ------------------------------------------------
>
>                 Key: MUSE-275
>                 URL: https://issues.apache.org/jira/browse/MUSE-275
>             Project: Muse
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>         Environment: Windows XP, OSGi
>            Reporter: Bert Lamb
>            Assignee: Dan Jemiolo
>             Fix For: 2.3.0
>
>         Attachments: content-type-fix.patch
>
>
> I have been working through creating client for a service I am exposing using the Muse mini platform.  My client complained about "Transport level information does not match with SOAP Message namespace URI" when parsing the responses from Muse.  I used TCPMon and sure enough Muse was setting the content type of the responses to "text/xml; charset=Cp1252" while the SOAP Envelope namespace was being set as xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
> This is a mismatch, SOAP 1.2 requires the content type to be "application/soap+xml"
> http://hadleynet.org/marc/whatsnew.html#S3.7.1
> It looks like my client library (using axis2) also requires the content encoding to be UTF-8.  So the Content-Type header on the responses from Muse should be:
> Content-Type: application/soap+xml; charset=UTF-8
> Looking at org.apache.muse.core.platform.mini.MiniServlet it looks like responses are currently hard coded to be "text/xml" which does not appear to be correct.
> I'm not sure if it is the best long term fix, but I will attach a patch that fixes this line to hard code to application/soap+xml instead.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@...
For additional commands, e-mail: muse-dev-help@...

     [ https://issues.apache.org/jira/browse/MUSE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bert Lamb updated MUSE-275:
---------------------------

    Component/s: Other

Not sure which component to assign to

> MiniServlet uses incorrect SOAP 1.1 content type
> ------------------------------------------------
>
>                 Key: MUSE-275
>                 URL: https://issues.apache.org/jira/browse/MUSE-275
>             Project: Muse
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 2.2.0
>         Environment: Windows XP, OSGi
>            Reporter: Bert Lamb
>            Assignee: Dan Jemiolo
>             Fix For: 2.3.0
>
>         Attachments: content-type-fix.patch
>
>
> I have been working through creating client for a service I am exposing using the Muse mini platform.  My client complained about "Transport level information does not match with SOAP Message namespace URI" when parsing the responses from Muse.  I used TCPMon and sure enough Muse was setting the content type of the responses to "text/xml; charset=Cp1252" while the SOAP Envelope namespace was being set as xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
> This is a mismatch, SOAP 1.2 requires the content type to be "application/soap+xml"
> http://hadleynet.org/marc/whatsnew.html#S3.7.1
> It looks like my client library (using axis2) also requires the content encoding to be UTF-8.  So the Content-Type header on the responses from Muse should be:
> Content-Type: application/soap+xml; charset=UTF-8
> Looking at org.apache.muse.core.platform.mini.MiniServlet it looks like responses are currently hard coded to be "text/xml" which does not appear to be correct.
> I'm not sure if it is the best long term fix, but I will attach a patch that fixes this line to hard code to application/soap+xml instead.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@...
For additional commands, e-mail: muse-dev-help@...

     [ https://issues.apache.org/jira/browse/MUSE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Twiner reassigned MUSE-275:
---------------------------------

    Assignee: Chris Twiner  (was: Dan Jemiolo)

> MiniServlet uses incorrect SOAP 1.1 content type
> ------------------------------------------------
>
>                 Key: MUSE-275
>                 URL: https://issues.apache.org/jira/browse/MUSE-275
>             Project: Muse
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 2.2.0
>         Environment: Windows XP, OSGi
>            Reporter: Bert Lamb
>            Assignee: Chris Twiner
>             Fix For: 2.3.0
>
>         Attachments: content-type-fix.patch
>
>
> I have been working through creating client for a service I am exposing using the Muse mini platform.  My client complained about "Transport level information does not match with SOAP Message namespace URI" when parsing the responses from Muse.  I used TCPMon and sure enough Muse was setting the content type of the responses to "text/xml; charset=Cp1252" while the SOAP Envelope namespace was being set as xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
> This is a mismatch, SOAP 1.2 requires the content type to be "application/soap+xml"
> http://hadleynet.org/marc/whatsnew.html#S3.7.1
> It looks like my client library (using axis2) also requires the content encoding to be UTF-8.  So the Content-Type header on the responses from Muse should be:
> Content-Type: application/soap+xml; charset=UTF-8
> Looking at org.apache.muse.core.platform.mini.MiniServlet it looks like responses are currently hard coded to be "text/xml" which does not appear to be correct.
> I'm not sure if it is the best long term fix, but I will attach a patch that fixes this line to hard code to application/soap+xml instead.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@...
For additional commands, e-mail: muse-dev-help@...

     [ https://issues.apache.org/jira/browse/MUSE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Twiner resolved MUSE-275.
-------------------------------

    Resolution: Fixed

in head.  NOTE that as Xerces is a direct dependency this works since OutputFormat defaults to UTF-8

> MiniServlet uses incorrect SOAP 1.1 content type
> ------------------------------------------------
>
>                 Key: MUSE-275
>                 URL: https://issues.apache.org/jira/browse/MUSE-275
>             Project: Muse
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 2.2.0
>         Environment: Windows XP, OSGi
>            Reporter: Bert Lamb
>            Assignee: Chris Twiner
>             Fix For: 2.2.1
>
>         Attachments: content-type-fix.patch
>
>
> I have been working through creating client for a service I am exposing using the Muse mini platform.  My client complained about "Transport level information does not match with SOAP Message namespace URI" when parsing the responses from Muse.  I used TCPMon and sure enough Muse was setting the content type of the responses to "text/xml; charset=Cp1252" while the SOAP Envelope namespace was being set as xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
> This is a mismatch, SOAP 1.2 requires the content type to be "application/soap+xml"
> http://hadleynet.org/marc/whatsnew.html#S3.7.1
> It looks like my client library (using axis2) also requires the content encoding to be UTF-8.  So the Content-Type header on the responses from Muse should be:
> Content-Type: application/soap+xml; charset=UTF-8
> Looking at org.apache.muse.core.platform.mini.MiniServlet it looks like responses are currently hard coded to be "text/xml" which does not appear to be correct.
> I'm not sure if it is the best long term fix, but I will attach a patch that fixes this line to hard code to application/soap+xml instead.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@...
For additional commands, e-mail: muse-dev-help@...