Bug 778663 (SOA-1136) - No port number in HOST header in outgoing request
Summary: No port number in HOST header in outgoing request
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1136
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP01
Assignee: Dana Mison
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-19 03:15 UTC by Taro Yasuma
Modified: 2009-03-18 16:04 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-18 16:04:08 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1136 0 Major Closed No port number in HOST header in outgoing request 2013-09-27 00:39:49 UTC

Description Taro Yasuma 2009-01-19 03:15:37 UTC
Date of First Response: 2009-02-16 20:42:47
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/254645
Workaround: Workaround Exists
Workaround Description: Set target-host-url under SOAPClient action which value has '-1' as port number.

Example)

<action name="soapui-client-action"
 class="org.jboss.soa.esb.actions.soap.SOAPClient">
 <property name="wsdl"
   value="http://server:8080/a/service?wsdl" >
   <http-client-property name="file" value="/path/to/httpclient.properties" />
 </property>
 ...
</action>

and httpclient.properties has a line:

target-host-url=http://server:-1
project_key: SOA

A outgoing request with using SOAPClient action results Host header without port number.

HOW TO REPRODUCE:

You can see this issue by running a simple example.

1.  configure httpclient and httpclient.wire.content category as DEBUG in jboss-log4j.xml to make output of HTTP headers:

For example)

   <category name="org.apache.commons.httpclient">
      <priority value="DEBUG"/>
   </category>
   <category name="httpclient.wire.content">
      <priority value="DEBUG"/>

2. run samples/quickstarts/webservice_consumer1.

For example)

$ant deploy
$ant runtest

3. Find debug output of the Host header in the server log.

For example)

2009-01-19 11:49:20,162 DEBUG [org.apache.commons.httpclient.HttpConnection] Open connection to 127.0.0.1:8080
2009-01-19 11:49:20,163 DEBUG [httpclient.wire.header] >> "GET /Quickstart_webservice_consumer1/HelloWorldWS?wsdl HTTP/1.1[\r][\n]"
2009-01-19 11:49:20,163 DEBUG [org.apache.commons.httpclient.HttpMethodBase] Adding Host request header
2009-01-19 11:49:20,163 DEBUG [httpclient.wire.header] >> "User-Agent: Jakarta Commons-HttpClient/3.0.1[\r][\n]"
2009-01-19 11:49:20,164 DEBUG [httpclient.wire.header] >> "Host: 127.0.0.1[\r][\n]"
2009-01-19 11:49:20,164 DEBUG [httpclient.wire.header] >> "[\r][\n]"
(snip)

Comment 1 Taro Yasuma 2009-01-19 04:47:31 UTC
Link: Added: This issue depends JBESB-2291


Comment 2 Dana Mison 2009-02-17 01:42:47 UTC
Release Note:
JBESB-2327 - SOAPClient outgoing requests now explicitly include a default port number (80 and 443 for http and https respectively) in the Host header if none is specified.


Comment 3 Jiri Pechanec 2009-03-12 12:09:34 UTC
Fixi is in place in CR4
nc -l 9090
GET /Quickstart_webservice_consumer1/HelloWorldWS?wsdl HTTP/1.1
User-Agent: Jakarta Commons-HttpClient/3.0.1
Host: 127.0.0.1:9090

But the text is missing from Release Notes


Comment 4 Dana Mison 2009-03-16 08:00:40 UTC
Release Notes have been submitted for QE, see SOA-1168


Comment 5 Len DiMaggio 2009-03-18 16:04:08 UTC
In the release note - page 10, section 9.3


Note You need to log in before you can comment on or make changes to this bug.