Bug 62480 - mod_proxy_wstunnel config needs the default port number
Summary: mod_proxy_wstunnel config needs the default port number
Status: RESOLVED FIXED
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.5-HEAD
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: PatchAvailable
Depends on:
Blocks:
 
Reported: 2018-06-21 11:32 UTC by Lubos Uhliarik
Modified: 2018-06-21 13:29 UTC (History)
0 users


Attachments
Add default schema ports (432 bytes, patch)
2018-06-21 11:32 UTC, Lubos Uhliarik 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lubos Uhliarik 2018-06-21 11:32:29 UTC 
Created attachment 35980 [details]
Add default schema ports

Hello,

in mod_proxy, you have to explicitly specify default port number for ws and wss scheme. 

Does 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

Attaching patch with the fix.
Comment 1 Lubos Uhliarik 2018-06-21 11:35:29 UTC 
I would like to also note, that without specifying the port, you can find following error in error_log:

[Thu Jun 21 07:02:50.545100 2018] [proxy:error] [pid 4072] (13)Permission denied: AH00957: WS: attempt to connect to 127.0.0.1:0 (127.0.0.1) failed
Comment 2 Jim Jagielski 2018-06-21 13:29:49 UTC 
Thanks! Committed revision 1834012

I did change the patch slightly to use the canon DEFINEs