Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 1. New features and enhancements

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.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

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.

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

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

Theme

© 2026 Red HatBack to top