Red Hat SummitRed Hat JBoss Core Services Apache HTTP Server 2.4.57 Service Pack 3 Release Notes
For Use with the Red Hat JBoss Core Services Apache HTTP Server 2.4.57
Abstract
Preface
Welcome to the Red Hat JBoss Core Services version 2.4.57 Service Pack 3 release.
Red Hat JBoss Core Services Apache HTTP Server is an open source web server developed by the Apache Software Foundation. The Apache HTTP Server includes the following features:
- Implements the current HTTP standards, including HTTP/1.1 and HTTP/2
- Supports Transport Layer Security (TLS) encryption through OpenSSL, which provides secure connections between the web server and web clients
- Supports extensible functionality through the use of modules, some of which are included with the Red Hat JBoss Core Services Apache HTTP Server
Providing feedback on Red Hat JBoss Core Services documentation
To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account.
Procedure
- Click the following link to create a ticket.
- Enter a brief description of the issue in the Summary.
- Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
- Clicking Submit creates and routes the issue to the appropriate documentation team.
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Chapter 1. New features and enhancements
Red Hat JBoss Core Services (JBCS) 2.4.57 Service Pack 3 includes the following new features and enhancements.
1.1. ResponseStatusCodeOnNoContext directive for mod_proxy_cluster
From the JBCS 2.4.57 Service Pack 3 release onward, the mod_proxy_cluster module also includes a ResponseStatusCodeOnNoContext directive. You can use the ResponseStatusCodeOnNoContext directive to specify the response status code that the server sends to the client when a ProxyPass or ProxyPassMatch directive does not have a matching context. The default status code is 404.
In JBCS 2.4.51 or earlier, when a ProxyPass or ProxyPassMatch directive did not have a matching context, the server sent a 503 status code by default. If you want to preserve the default behavior that was available in earlier releases, set the ResponseStatusCodeOnNoContext directive to 503 instead.
If you specify a value other than a standard HTTP response code, the server access log shows the specified value but the server sends a 500 Internal Server Error response to the client.
Chapter 2. Installing the Red Hat JBoss Core Services 2.4.57
You can install the Apache HTTP Server 2.4.57 on Red Hat Enterprise Linux or Windows Server. For more information, see the following sections of the installation guide:
Chapter 3. Upgrading to the Red Hat JBoss Core Services Apache HTTP Server 2.4.57
The steps to upgrade to the latest Red Hat JBoss Core Services (JBCS) release differ depending on whether you previously installed JBCS from RPM packages or from an archive file.
Upgrading JBCS when installed from RPM packages
If you installed an earlier release of the JBCS Apache HTTP Server from RPM packages on RHEL 7 or RHEL 8 by using the yum groupinstall command, you can upgrade to the latest release. You can use the yum groupupdate command to upgrade to the 2.4.57 release on RHEL 7 or RHEL 8.
JBCS does not provide an RPM distribution of the Apache HTTP Server on RHEL 9.
Upgrading JBCS when installed from an archive file
If you installed an earlier release of the JBCS Apache HTTP Server from an archive file, you must perform the following steps to upgrade to the Apache HTTP Server 2.4.57:
- Install the Apache HTTP Server 2.4.57.
- Set up the Apache HTTP Server 2.4.57.
- Remove the earlier version of Apache HTTP Server.
The following procedure describes the recommended steps for upgrading a JBCS Apache HTTP Server 2.4.51 release that you installed from archive files to the latest 2.4.57 release.
Prerequisites
- If you are using Red Hat Enterprise Linux, you have root user access.
- If you are using Windows Server, you have administrative access.
- The Red Hat JBoss Core Services Apache HTTP Server 2.4.51 or earlier was previously installed in your system from an archive file.
Procedure
- Shut down any running instances of Red Hat JBoss Core Services Apache HTTP Server 2.4.51.
- Back up the Red Hat JBoss Core Services Apache HTTP Server 2.4.51 installation and configuration files.
- Install the Red Hat JBoss Core Services Apache HTTP Server 2.4.57 using the .zip installation method for the current system (see Additional Resources below).
Migrate your configuration from the Red Hat JBoss Core Services Apache HTTP Server version 2.4.51 to version 2.4.57.
NoteThe Apache HTTP Server configuration files might have changed since the Apache HTTP Server 2.4.51 release. Consider updating the 2.4.57 version configuration files rather than overwrite them with the configuration files from a different version, such as the Apache HTTP Server 2.4.51.
- Remove the Red Hat JBoss Core Services Apache HTTP Server 2.4.51 root directory.
Additional Resources
Chapter 4. Resolved issues
The following issues are resolved for this release:
| Issue | Summary |
|---|---|
| [RHEL9] Upgrade mod_jk to 1.2.49 to be in sync with the version used by all other JBCS releases | |
| [RHEL9] Upgrade mod_proxy_cluster to 1.3.20 to be in sync with the version used by all other JBCS releases | |
| mod_proxy_cluster returns 404 now instead of 503 when there’s no matching context | |
| jbcs-httpd24-httpd has no dependency to jbcs-httpd24-brotli | |
| mod_cluster leaks memory with httpd 2.4.53+ | |
| mod_cluster returns rare but unexpected 404/503 | |
| [Doc] Review the prerequisite package for RHEL8 |
For details of any security fixes in this release, see the errata links in Advisories related to this release.
Chapter 5. Known issues
There are no known issues for this release.
Chapter 6. Supported components
For a full list of component versions that are supported in this release of Red Hat JBoss Core Services, see the Core Services Apache HTTP Server Component Details page. Before you attempt to access the Component Details page, you must ensure that you have an active Red Hat subscription and you are logged in to the Red Hat Customer Portal.
Chapter 7. Advisories related to this release
The following advisories have been issued to document enhancements, bugfixes, and CVE fixes included in this release.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}