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 1224775 - wrong default port for fcgi
Summary: wrong default port for fcgi
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: httpd
Version: 7.2
Hardware: All
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Luboš Uhliarik
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On: 1224763
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-25 16:12 UTC by Ondřej Pták
Modified: 2017-02-07 08:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1224763
Environment:
Last Closed: 2017-02-07 08:59:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ondřej Pták 2015-05-25 16:12:08 UTC
+++ This bug was initially created as a clone of Bug #1224763 +++

Description of problem:
When using mod_proxy with php-fpm and, httpd use port 8000 instead of 9000 as default for fcgi protocol.
This is hardcoded in: httpd-2.4.12/modules/proxy/proxy_util.c

Version-Release number of selected component (if applicable):
httpd-2.4.6-31.el7

How reproducible:
always

Steps to Reproduce:
1. use linked test, but remove all port definition from configuration (fpm.conf)

Actual results:
http code 503

Expected results:
http code 200

Additional info:

error_log:
[Mon May 25 12:05:07.665370 2015] [proxy:error] [pid 15945] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:8000 (127.0.0.1) failed
[Mon May 25 12:05:07.665394 2015] [proxy:error] [pid 15945] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 60s

Comment 2 Jan Kaluža 2015-07-10 10:52:37 UTC
There is no standard port for FCGI. It is true that the php-fpm (which is deployed quite often) uses port 9000, so we could use this port as default, but there is nothing like "default fcgi port". We will try to bring this discussion upstream and change the default to match php-fpm in upstream, but it's not something we would like to do in 7.2 without upstream right now. Moving to 7.3

Comment 6 Joe Orton 2017-02-07 08:59:48 UTC
Upstream still use port 8000 as the default port mapping for fcgi://.  Changing
the implicit default is potentially a backwards compat break so we'd need very
good motivation to change it in RHSCL.

Plus both 8000 and 9000 are IETF reserved ports... unlikely we'll patch
anything in here.


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