Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Look & Feel Configuration popup displays error upon saving when using HTTP2

Written By

Anishq Sharma

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

  • Look & Feel Configuration popup displays below error upon saving when using HTTP2: 
    Your settings could not be saved
  • Steps to reproduce:
    • Configure the App server to work with HTTP/2.

    • Open the Look & Feel configuration of any portlet, make some changes and save it.

  • Expected Behavior: Changes are saved without error message.
  • Observed Behavior: User gets error message 'Your settings could not be saved'. However, the changes get saved.
  • The behavior is only reproducible with HTTP/2.
  • The behavior is only reproducible with Tomcat 8.5 and above, as Tomcat 8.0 does not support HTTP/2.

Environment

  • Liferay DXP 7.1
  • Liferay DXP 7.2
  • Liferay DXP 7.3
  • Liferay DXP 7.4

Resolution

  • The observed behavior is a known issue/bug and is resolved through LPS-93358. 
  • If the Hotfix is required for this issue, please create a support ticket requesting Hotfix by attaching patch details.
  • Installing Fix Packs and Hotfixes on Liferay DXP will guide to installation of the hotfix in the respective environment.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?