Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UTF-8 encoding issue #505

Open
iheos opened this issue Jan 15, 2020 · 0 comments
Open

UTF-8 encoding issue #505

iheos opened this issue Jan 15, 2020 · 0 comments
Assignees

Comments

@iheos
Copy link
Contributor

iheos commented Jan 15, 2020

I found the reason why the parser is not detecting the document's encoding, it's because the tool is not returning the charset in the MIME Content Type of the part that contains the document (only in the part that contains the SOAP response).

Here's a sample response from the tool for a RetrieveDocumentSet request:

--MIMEBoundary112233445566778899
Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml"
Content-Transfer-Encoding: binary
Content-ID: [email protected]

<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"><S:Header><wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:s="http://www.w3.org/2003/05/soap-envelope" s:mustUnderstand="1">urn:ihe:iti:2007:RetrieveDocumentSetResponse</wsa:Action><wsa:RelatesTo xmlns:wsa="http://www.w3.org/2005/08/addressing">urn:uuid:a45b7932-ed23-4672-96b8-5957f504ff1b</wsa:RelatesTo></S:Header><S:Body><xdsb:RetrieveDocumentSetResponse xmlns:xdsb="urn:ihe:iti:xds-b:2007"><rs:RegistryResponse xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success"/>xdsb:DocumentResponsexdsb:RepositoryUniqueId1.1.4567332.1.1</xdsb:RepositoryUniqueId>xdsb:DocumentUniqueId2.16.840.1.113883.3.3731.1.203.14^1311446</xdsb:DocumentUniqueId>xdsb:mimeTypetext/plain</xdsb:mimeType>xdsb:Document<xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:[email protected]"/></xdsb:Document></xdsb:DocumentResponse></xdsb:RetrieveDocumentSetResponse></S:Body></S:Envelope>

--MIMEBoundary112233445566778899
Content-Type: text/plain
Content-Transfer-Encoding: binary
Content-ID: [email protected]


--MIMEBoundary112233445566778899--

Is this an issue that could be fixed in a future release or am I missing something here?

@iheos iheos self-assigned this Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant