Legacy Knowledge Base
Published Jul. 2, 2025

F5 web server device blocks Liferay URL with message: "Bad multipart parameters parsing / No boundary defined for multipart request"

Written By

Alfonso Crisci

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.

Issue

  • A F5 web server device (for example, a load balancer) blocks a Liferay URL with messages like:

    Bad multipart parameters parsing
    No boundary defined for multipart request
    Flagging the request to process the URL as a violation.

Environment

  • Liferay DXP 7.0+

Resolution

Additional Information

  • Bad multipart parameters parsing
    From F5 docs https://support.f5.com/csp/article/K10280:

    The system examines the requests to verify that the Content-Disposition header matches the format: name="param_key";\r\n.
    The system also checks that the following is true:

  • A boundary follows immediately after the request headers.
  • The parameter value matches the format: ‘name="param_key";\r\n.
  • A chunked body contains at least one CRLF.
  • A chunked body ends with CRLF.

    If one of these is false, a violation is issued.

  • No boundary defined for multipart request
    From F5 docs https://support.f5.com/csp/article/K44162352:

  • There is no boundary delimiter defined for the multipart request.
Did this article resolve your issue ?

Legacy Knowledge Base