Legacy Knowledge Base
Published Jul. 2, 2025

AJP Sends Body With Status 304 If Using Tomcat 7.0.42

Written By

Michael Warren Young

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

This article documents a reported status code of 304 when using Apache 2 and Tomcat 7.0.42 connected via mod_proxy_ajp. In addition, the article provides a solution to fix the bug.

Resolution

The status code 304 is caused by a bug in Tomcat 7.0.42 and can be fixed with Tomcat 7.0.43 or any other later version. Please note that beginning with Liferay Portal 6.2.x EE SP13, Liferay's Tomcat bundles use Tomcat 7.0.62.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base