Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.3-rc2
-
Component/s: Transport: HTTP(S) / Jetty
-
Labels:None
-
Environment:
Windowz XP
-
Log Output:
-
Similar Issues:
MULE-1162HTTP message headers are coppied between the routers via the UMOMessage propertyMULE-3162duplicate message properties files
MULE-3756 support sending files via xmppMULE-2681Stockquote SOAP excluded via messaging-apiMULE-1767RestServiceWrapper ignores HTTP_METHOD_PROPERTYMULE-4533CXF endpoint properties get copied into HTTP messages
MULE-4628 Multiple XaTransactedJmsMessageReceiver are created for topics resulting in duplicate delivery fo messageMULE-3999Don't copy session properties to the messageMULE-4988The HTTP message factory still copies some properties to the outbound scopeMULE-1987Reply-to property being handled to early in message flow
Description
After fixing a ClassCastException related to Cookies I noticed duplicate message properties showing up - I think something has gone wrong with the way X-MULE and MULE headers are processed. Not sure if this used to work, i.e if the X-MULE headers used to show up or if they are even supposed to.
Example for POJO roundtrip via HTTP over local VM trampoline to avoid accessing the URL directly. Can be added to the samples after cleanup/review.