Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: 2.0.0-RC2
-
Fix Version/s: 2.0.1
-
Component/s: Examples / Tutorials, Transport: HTTP(S) / Jetty
-
Labels:None
-
User impact:Medium
-
Similar Issues:
MULE-5504Content-Type header not set with PUT methodMULE-3552Webapp "REST Put/Get" example does not workMULE-4805Mule webapp REST PUT/GET example failsMULE-5610Content-Type header not set with PUT methodMULE-3979ContentType should be Content-typeMULE-2764Webapp example throws SAXParseException: Content is not allowed in prolog.MULE-4031Content-Type of "text/xml" is getting propagated from previous messageMULE-4047Default Content-Type setting on Mule Servlet gets ignoredMULE-4180Webapp example REST support is broken on embedded TomcatMULE-4439webapp example fails for 'REST Hello World'
Description
Running the webapp examples and using the "PUT" example results in the response being downloaded as a file rather than displayed in the browser.
Dan, there was this very old issue I can't find now. The behavior differed for among browsers. The workaround was to add a MessagePropertiesTransformer and fix the content type to text/plain or text/html on the response.