legacy-knowledge-base
Publicado Jul. 25, 2002

HTTP 400 response code shows sensitive data

written-by

Phil Chapman

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

learn-legacy-article-disclaimer-text

Issue

  • Sensitive system information may be seen in HTTP 400 - Bad Response status


Environment

  • DXP 7.0   DXP 7.1   DXP 7.2

Resolution

The HyperText Transfer Protocol (HTTP) 400 Bad Request response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

To resolve:

  1. Attempt to fix the 400 status error by investigating the ideas mentioned (above)

  2. Hide the 400 status code page 

  3. Redirect the 400 error to a custom error page
    Here is a sample resource on how this may be achieved, see section: "Tomcat 9 has improved the error handling..."

    https://stackoverflow.com/questions/52814582/tomcat-is-not-redirecting-to-400-bad-request-custom-error-page/55702749#55702749 


Additional Information

 

did-this-article-resolve-your-issue

legacy-knowledge-base