Replies: 3 comments 5 replies
-
I can confirm that this only happens in mirth, and not in vanilla Rhino. I suspect it has to do with this patch. 1b42342 |
Beta Was this translation helpful? Give feedback.
3 replies
-
Does your use case require HTML or can you send XHTML? If you can send XHTML, do that since it is XML already. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Oh, you're right. I think the last time I dealt with this issue my team had to get XHTML then treat it as text to add the correct XML header or doctype declarations. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I created a HTTP listener channel that responds with simple, pure and very old-school HTML. My source transformer outbound message template is XML data type (for easy modification using E4X) and looks as follows:
Now, the problem is that Mirth adds some tags in the final outbound message:
... and this leads to a parsing error in the destination's inbound message (link):
I didn't add these tags to the
tmp
variable and I don't want Mirth to add something that I didn't define.So why is that? And how can I prevent Mirth doing this?
Beta Was this translation helpful? Give feedback.
All reactions