[esb-issues] [JBoss JIRA] Commented: (JBESB-3627) http_2way_ssl quickstart doesn't pass the HTTP header through JBR in the action chain

http_2way_ssl quickstart doesn't pass the HTTP header through JBR in the action chain ------------------------------------------------------------------------------------- Key: JBESB-3627 URL: https://issues.jboss.org/browse/JBESB-3627 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Web Services Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 There is an issue in "http_2way_ssl" quickstart (that is a part of SOA-P distribution). In the case of SOA-P 4.3.0_CP04 the HTTP header ("blah: blahval") that is configured/provided by HTTPRouter in the ESB action chain passes all the way to client response and its presence is confirmed in the server's log where the quickstart prints the output. But in the case of SOA-P v5 the header is not passed to the end of ESB action chain. The quickstart practically wasn't changed between the SOA-P versions. SOA-P 4.3.0_CP04.GA - quickstart's output in server's log: ... 15:35:51,886 INFO [STDOUT] =========== Server Request: ==================================== 15:35:51,886 INFO [STDOUT] Message Payload: 15:35:51,886 INFO [STDOUT] [Request Payload!] 15:35:51,886 INFO [STDOUT] Headers: 15:35:51,886 INFO [STDOUT] host: localhost 15:35:51,886 INFO [STDOUT] Method: POST 15:35:51,886 INFO [STDOUT] Path: /x/y 15:35:51,886 INFO [STDOUT] user-agent: Jakarta Commons-HttpClient/3.0.1 15:35:51,887 INFO [STDOUT] content-type: text/xml;charset=UTF-8 15:35:51,887 INFO [STDOUT] ================================================================ 15:35:51,940 INFO [STDOUT] =========== Client Response: =================================== 15:35:51,940 INFO [STDOUT] Message Payload: 15:35:51,940 INFO [STDOUT] [Http Response Payload!!] 15:35:51,940 INFO [STDOUT] Http Response: 15:35:51,940 INFO [STDOUT] Code: 200 15:35:51,940 INFO [STDOUT] Length: 23 15:35:51,940 INFO [STDOUT] Encoding: ISO-8859-1 15:35:51,940 INFO [STDOUT] Headers: 15:35:51,940 INFO [STDOUT] blah: blahval 15:35:51,940 INFO [STDOUT] Content-Type: text/xml;charset=UTF-8 15:35:51,940 INFO [STDOUT] User-Agent: Jakarta Commons-HttpClient/3.0.1 15:35:51,940 INFO [STDOUT] Host: localhost 15:35:51,940 INFO [STDOUT] Content-Length: 16 15:35:51,940 INFO [STDOUT] ================================================================ ... SOA-P 5.1.0.ER2 - quickstart's output in server's log: ... 15:44:22,936 INFO [STDOUT] =========== Server Request: ==================================== 15:44:22,936 INFO [STDOUT] Message Payload: 15:44:22,937 INFO [STDOUT] [Request Payload!] 15:44:22,938 INFO [STDOUT] Headers: 15:44:22,972 INFO [STDOUT] host: localhost:9433 15:44:22,972 INFO [STDOUT] Method: POST 15:44:22,972 INFO [STDOUT] Path: /x/y 15:44:22,973 INFO [STDOUT] user-agent: Jakarta Commons-HttpClient/3.0.1 15:44:22,973 INFO [STDOUT] content-type: text/xml;charset=UTF-8 15:44:22,973 INFO [STDOUT] ================================================================ 15:44:23,040 INFO [STDOUT] =========== Client Response: =================================== 15:44:23,040 INFO [STDOUT] Message Payload: 15:44:23,040 INFO [STDOUT] [Http Response Payload!!] 15:44:23,085 INFO [STDOUT] Http Response: 15:44:23,085 INFO [STDOUT] Code: 200 15:44:23,085 INFO [STDOUT] Length: 23 15:44:23,085 INFO [STDOUT] Encoding: ISO-8859-1 15:44:23,086 INFO [STDOUT] Headers: 15:44:23,086 INFO [STDOUT] Server: Apache-Coyote/1.1 15:44:23,086 INFO [STDOUT] ResponseCode: 200 15:44:23,086 INFO [STDOUT] ResponseCodeMessage: OK 15:44:23,086 INFO [STDOUT] remotingContentType: remotingContentTypeString 15:44:23,086 INFO [STDOUT] Content-Type: text/html 15:44:23,086 INFO [STDOUT] Content-Length: 23 15:44:23,086 INFO [STDOUT] Date: Wed, 13 Oct 2010 13:44:22 GMT 15:44:23,087 INFO [STDOUT] ================================================================ ...