We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-43340

Unable to set page restrictions due to large number of user keys in http header

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Summary

      Attempting to edit page restrictions when a large number of users are listed prevents the changes from being saved. This appears to be due to Confluence putting the full list of user numbers in the http header, which means the size exceeds the maximum default for Tomcat (4KB), which causes Confluence to return a 404 page not found.

      Environment

      • Confluence 5.9.11

      Steps to Reproduce

      1. Create a new page
      2. Edit the page restrictions, add 61 users to view permission and 61 users to view/edit permission
      3. Try to apply the restriction change

      Expected Results

      The modification should be saved.

      Actual Results

      It is showing an error on the restriction popup without any detail message.

      There was an error submitting the page restrictions. Please try again later.

      See HAR findings in private comment below

      Workaround

      As a short term workaround solution, you can either chose to use a group instead of individual users, or increase the header size limitation on both Tomcat and at the proxy level.

      For example, add the following in your server.xml connector(s):

      maxHttpHeaderSize="1048576"
      
      • This is 1048576 bytes, or 1MB

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Confluence Data Center'
            1. Confluence Data Center
            2. CONFSERVER-43340

            Unable to set page restrictions due to large number of user keys in http header

                NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

                Summary

                Attempting to edit page restrictions when a large number of users are listed prevents the changes from being saved. This appears to be due to Confluence putting the full list of user numbers in the http header, which means the size exceeds the maximum default for Tomcat (4KB), which causes Confluence to return a 404 page not found.

                Environment

                • Confluence 5.9.11

                Steps to Reproduce

                1. Create a new page
                2. Edit the page restrictions, add 61 users to view permission and 61 users to view/edit permission
                3. Try to apply the restriction change

                Expected Results

                The modification should be saved.

                Actual Results

                It is showing an error on the restriction popup without any detail message.

                There was an error submitting the page restrictions. Please try again later.

                See HAR findings in private comment below

                Workaround

                As a short term workaround solution, you can either chose to use a group instead of individual users, or increase the header size limitation on both Tomcat and at the proxy level.

                For example, add the following in your server.xml connector(s):

                maxHttpHeaderSize="1048576"
                
                • This is 1048576 bytes, or 1MB

                        Unassigned Unassigned
                        jwyllys Justin W.
                        Votes:
                        9 Vote for this issue
                        Watchers:
                        17 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            jwyllys Justin W.
                            Affected customers:
                            9 This affects my team
                            Watchers:
                            17 Start watching this issue

                              Created:
                              Updated:
                              Resolved: