[
https://jira.jboss.org/jira/browse/JBESB-2511?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-2511:
-----------------------------------
All the response headers should find their way back out, but for now (for my ws proxy
work), the only one that appears to be a problem is Content-Type. The HttpRouter (once I
change it to method.getResponseHeaders()) is getting back
"text/xml;charset=UTF-8", however the caller of the JBR gateway is getting
"Content-Type: text/html
".
HttpRouter is inconsistent in its handling of response headers
--------------------------------------------------------------
Key: JBESB-2511
URL:
https://jira.jboss.org/jira/browse/JBESB-2511
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.5
Reporter: Rune Molin
Assignee: Tom Fennelly
Fix For: 4.6
org.jboss.soa.esb.actions.routing.http.HttpRouter places http response headers in the
body of the message. The JBR Gateway expects http response headers to be in the message
properties, meaning the two can not easily be combined into a simple webservice proxy
service.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira