RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1556761 - mod_proxy_wstunnel config needs the default port number
Summary: mod_proxy_wstunnel config needs the default port number
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: httpd
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Luboš Uhliarik
QA Contact: Jan Houska
URL:
Whiteboard:
Depends On:
Blocks: 1549616 2074492
TreeView+ depends on / blocked
 
Reported: 2018-03-15 08:39 UTC by Hisanobu Okuda
Modified: 2022-04-12 10:54 UTC (History)
4 users (show)

Fixed In Version: httpd-2.4.6-85.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2074492 (view as bug list)
Environment:
Last Closed: 2018-10-30 11:19:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3211 0 None None None 2018-10-30 11:19:53 UTC

Description Hisanobu Okuda 2018-03-15 08:39:39 UTC 
Description of problem:


Not work:
        BalancerMember  ws://127.0.0.1 ping=1 connectiontimeout=3 route=1

Does work:
        BalancerMember  ws://127.0.0.1:80 ping=1 connectiontimeout=3 route=1


Version-Release number of selected component (if applicable):

    httpd-2.4.6-80.el7.x86_64

How reproducible:


Steps to Reproduce:
1. install httpd and tomcat8
2. configure tomcat to use the port 80
 # vim /etc/tomcat/server.xml
 72     <Connector port="80" protocol="HTTP/1.1" address="0.0.0.0"
 73                connectionTimeout="20000"
 74     />

3. run tomcat as root

 # /usr/lib/jvm/jre/bin/java -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.m
anagement.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=true -Dcom.sun.management.jmxremote.registry.ssl=true -Djavax.
net.ssl.keyStorePassword=password -Djavax.net.ssl.keyStore=/etc/tomcat/keystore -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr/shar
e/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat -Dja
va.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat/temp -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Dja
va.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start

4. configure httpd to use the port 81

Listen 81

5. copy the following proxy.conf to /etc/httpd/conf.d

LogLevel trace8

ProxyPass               /examples/websocket/     balancer://clusterwss/examples/websocket/
ProxyPassReverse        /examples/websocket/     balancer://clusterwss/examples/websocket/
ProxyPass               /       balancer://cluster/
ProxyPassReverse        /       balancer://cluster/

<Proxy balancer://cluster>
        BalancerMember  http://127.0.0.1 ping=1 connectiontimeout=3 route=1
</Proxy>
<Proxy balancer://clusterwss>
        BalancerMember  ws://127.0.0.1 ping=1 connectiontimeout=3 route=1
</Proxy>

6. start httpd

7. access http://localhost:81/examples/websocket/echo.xhtml

8. click programmatic API and the connect button

9. You will get the following error message:

[Thu Mar 15 17:10:22.796580 2018] [proxy:error] [pid 30466] (111)Connection refused: AH00957: WS: attempt to connect to 127.0.0.1:0 (127
.0.0.1) failed

10. change the proxy.conf which is created in the step 5 as follows(add :80)

<Proxy balancer://clusterwss>
        BalancerMember  ws://127.0.0.1:80 ping=1 connectiontimeout=3 route=1
</Proxy>

11. restart httpd

7. access http://localhost:81/examples/websocket/echo.xhtml

8. click programmatic API and the connect button, then you will see the websocket connection is establishded.

Actual results:


Expected results:


Additional info:
Comment 1 Oneata Mircea Teodor 2018-03-15 10:13:40 UTC 
This is an illegal clone as is forbidden to create BZ z stream directly. Zstream fixes are cloned from Y stream BZ.
Please check the documentation.
https://mojo.redhat.com/docs/DOC-1021938#jive_content_id_Executive_Summary
Comment 8 Jan Houska 2018-08-31 10:29:39 UTC 
VERIFIED

NEW pass:
httpd-2.4.6-88.el7

https://beaker.engineering.redhat.com/tasks/executed?recipe_task_id=78395253&recipe_task_id=78395246&recipe_task_id=78350182&recipe_task_id=78350189&recipe_task_id=78350175&recipe_task_id=78408523&new_pkg_tasks=78395253,78395246,78350182,78350189,78350175,78408523

and 

https://beaker.engineering.redhat.com/tasks/executed?recipe_task_id=78350220&recipe_task_id=78350208&recipe_task_id=78350214&recipe_task_id=78350226&new_pkg_tasks=78350220,78350208,78350214,78350226
Comment 10 errata-xmlrpc 2018-10-30 11:19:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3211
Note You need to log in before you can comment on or make changes to this bug.