Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Red Hat JBoss Core Services Apache HTTP Server 2.4.51 Service Pack 2 Release Notes

Red Hat JBoss Core Services 2.4.51

For Use with the Red Hat JBoss Core Services Apache HTTP Server 2.4.51

Red Hat Customer Content Services

Abstract

These release notes contain important information related to the Red Hat JBoss Core Services Apache HTTP Server 2.4.51.

Preface
Copy link

Welcome to the Red Hat JBoss Core Services version 2.4.51 Service Pack 2 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 documentation
Copy link

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

  1. Click the following link to create a ticket.
  2. Enter a brief description of the issue in the Summary.
  3. Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
  4. Clicking Submit creates and routes the issue to the appropriate documentation team.

Making open source more inclusive
Copy link

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
Copy link

Red Hat JBoss Core Services (JBCS) 2.4.51 Service Pack 2 includes the following new features and enhancements.

1.1. Red Hat Enterprise Linux 9 support
Copy link

From the 2.4.51 Service Pack 2 release onward, JBCS is also certified for use on Red Hat Enterprise Linux (RHEL) 9.

Important

Support is available for installing JBCS on RHEL 9 from an archive file only. JBCS does not provide an RPM distribution of the Apache HTTP Server for RHEL 9 systems.

If you want to install the Apache HTTP Server from RPM packages on RHEL 9, you can use the Application Streams feature of RHEL. For more information about the different installation options, see the Red Hat JBoss Core Services Apache HTTP Server Installation Guide.

For JBCS Apache HTTP Server installations on RHEL 9, the supported Apache HTTP Server version is 2.4.53.

Note

The base archive file for installing the JBCS Apache HTTP Server on RHEL 9 is named Red Hat JBoss Core Services Apache HTTP Server 2.4.51 Patch 02 for RHEL 9 x86_64. Despite the 2.4.51 naming convention, the JBCS archive file for RHEL 9 provides a distribution of Apache HTTP Server 2.4.53.

1.3. UseNocanon directive for mod_proxy_cluster
Copy link

The mod_proxy_cluster module now supports a UseNocanon directive that enables you to define whether you want the proxy to forward the original URL path to the back end without modifications.

The default value is Off. When the UseNocanon directive is set to Off, the proxy can forward modified URLs to the back end. However, if the back-end application expects the original URL path that the client requested, the modified URL path can lead to unexpected issues.

When you set the UseNocanon directive to On, the proxy can forward the original URL path to the back end without any modifications. In this situation, the proxy behavior depends on whether you also define a context and a ProxyPass directive for the requested URL in the mod_proxy_cluster.conf file. A context is also known as a virtual host definition.

Consider the following guidelines when you set the UseNocanon directive to On:

  • If you define a context for the requested URL but you do not define a ProxyPass directive for this URL, the proxy uses the UseNocanon directive.
  • If you define both a context and a ProxyPass directive for the requested URL, and the ProxyPass directive includes the nocanon flag, the proxy uses the nocanon flag and ignores the UseNocanon directive.
  • If you define both a context and a ProxyPass directive for the requested URL, and the ProxyPass directive excludes the nocanon flag, the proxy ignores the UseNocanon directive.
Note

If you do not define a context for the requested URL, mod_proxy_cluster returns a 404 error.

Unlike JBCS 2.4.51 on RHEL 7 or RHEL 8, the JBCS 2.4.51 distribution for RHEL 9 systems is based on the RHEL distribution of the Apache HTTP Server httpd package.

Because of this difference between the JBCS 2.4.51 distributions for different RHEL versions, JBCS 2.4.51 on RHEL 9 has certain behavioral differences compared to JBCS 2.4.51 on earlier RHEL versions.

Consider the following guidelines:

  • On RHEL 9, the mod_security module does not support the SecCollectionGCFrequency directive for specifying garbage collection frequency. The mod_security module that JBCS provides on RHEL 7 and RHEL 8 supports the SecCollectionGCFrequency directive.
  • On RHEL 9, the mod_deflate module does not support the DeflateAlterEtag directive for specifying how to alter the ETag header when a response is compressed. The mod_deflate module that JBCS provides on RHEL 7 and RHEL 8 supports the DeflateAlterEtag directive.

  • On RHEL 9, the httpd.conf.sample file does not include the following content:

    • A default PidFile directive for specifying the file in which the server records the process ID of the daemon
    • A list of AddLanguage directives in the mod_mime section for mapping specific filename extensions to specific content languages
    • A configuration section for the web_dav module for web-based distributed authoring and versioning (WebDav)

    The httpd.conf.sample file that JBCS provides on RHEL 7 and RHEL 8 includes all of the preceding content.

You can install the Apache HTTP Server 2.4.51 on Red Hat Enterprise Linux (RHEL) or Windows Server systems. For more information, see the following sections of the installation guide:

Note

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.51 release on RHEL 7 or RHEL 8.

JBCS does not provide an RPM distribution of the Apache HTTP Server on RHEL 9.

If you installed an earlier release of the JBCS Apache HTTP Server from archive files, upgrading to the Apache HTTP Server 2.4.51 release requires the following steps:

  1. Installing the Apache HTTP Server 2.4.51
  2. Setting up the Apache HTTP Server 2.4.51
  3. Removing the earlier version of Apache HTTP Server

The following procedure describes the recommended steps for upgrading a JBCS Apache HTTP Server 2.4.37 release that you installed from archive files to the latest 2.4.51 release.

Prerequisites

  • Root user access (Red Hat Enterprise Linux systems)
  • Administrative access (Windows Server)
  • A system where the Red Hat JBoss Core Services Apache HTTP Server 2.4.37 or earlier was installed from archive files

Procedure

  1. Shut down any running instances of Red Hat JBoss Core Services Apache HTTP Server 2.4.37.
  2. Back up the Red Hat JBoss Core Services Apache HTTP Server 2.4.37 installation and configuration files.
  3. Install the Red Hat JBoss Core Services Apache HTTP Server 2.4.51 using the .zip installation method for the current system (see Additional Resources below).

  4. Migrate your configuration from the Red Hat JBoss Core Services Apache HTTP Server version 2.4.37 to version 2.4.51.

    Note

    The Apache HTTP Server configuration files might have changed since the Apache HTTP Server 2.4.37 release. Consider updating the 2.4.51 version configuration files rather than overwrite them with the configuration files from a different version, such as the Apache HTTP Server 2.4.37.

  5. Remove the Red Hat JBoss Core Services Apache HTTP Server 2.4.37 root directory.

Additional Resources

Chapter 5. Resolved issues
Copy link

The following issues are resolved for this release:

Expand
IssueSummary

JBCS-1454

httpd 2.4.51 rpm apachectl no longer uses systemctl commands

JBCS-1427

Error in Windows event log after stopping JBoss EAP 7.3.6 service

JBCS-1261

prunsrv with force stop option

JBCS-1092

Shutdown log and CLI result are mixed up on stdout when stopping EAP as a windows service

JBCS-450

mod_cluster balancers to be able to support nocanon flag

JBCS-392

mod_proxy_hcheck doesn’t perform checks

Chapter 6. Known issues
Copy link

No known issues affect this release.

Chapter 7. Supported components
Copy link

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.

Legal Notice
Copy link

Copyright © 2024 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Legal Notice

Theme

© 2026 Red HatBack to top