[
https://issues.apache.org/jira/browse/WSCOMMONS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen reassigned WSCOMMONS-200:
-----------------------------------------
Assignee: Andreas Veithen
The problem is that TCPMon doesn't examine the structure of the HTTP request it
is intercepting (at least not in the stage where the XML formatting happens).
It just blindly looks for "<", "</" and "/>" sequences anywhere in the request.
In order to enable XML formatting only for the appropriate portions of the
request, TCPMon would have to:
* Decode the transfer encoding (e.g. chunked).
* Detect the content type.
* Detect MIME boundaries and MIME headers in multipart/related messages.
This is not trivial. However, I recently refactored some of the code in TCPMon
to have a cleaner design and this could now be envisaged.
> XML format option formats attachments even if they are not xml documents
> ------------------------------------------------------------------------
>
> Key: WSCOMMONS-200
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-200
> Project: WS-Commons
> Issue Type: Bug
> Components: TCPMon
> Reporter: Jorge Fernández
> Assignee: Andreas Veithen
> Priority: Trivial
>
> When sending attachments, like a image, sometimes it has the symbol "<" so
> TCPMon thinks it is the start of a tag and tabulates it
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
