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.
Jira Data CenterProject Type: software

Jira Data Center

Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-70733

Allow setting maxHttpHeaderSize by environment variable in jira-software docker image

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • None
    • Tomcat
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      As default maxHttpHeaderSize value is 8192 and cannot be changed, we have to create customised docker image based on https://bitbucket.org/atlassian-docker/docker-atlassian-jira to allow the value to be increased to avoid below error

      HTTP Status 400 – Bad Request
Type Exception Report

Message Request header is too large

Description 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).

Exception

java.lang.IllegalArgumentException: Request header is too large
	org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:726)
	org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:873)
	org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:579)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:700)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:808)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Unknown Source)
Note The full stack trace of the root cause is available in the server logs.

Apache Tomcat/8.5.42

      There was a similar one reported for Confluence docker image at https://jira.atlassian.com/browse/CONFSERVER-59318

            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: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-70733

            Allow setting maxHttpHeaderSize by environment variable in jira-software docker image

            XMLWordPrintable

              • Icon: Suggestion Suggestion
              • Resolution: Done
              • None
              • Tomcat
              • None
              • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

                As default maxHttpHeaderSize value is 8192 and cannot be changed, we have to create customised docker image based on https://bitbucket.org/atlassian-docker/docker-atlassian-jira to allow the value to be increased to avoid below error

                HTTP Status 400 – Bad Request
Type Exception Report

Message Request header is too large

Description 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).

Exception

java.lang.IllegalArgumentException: Request header is too large
	org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:726)
	org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:873)
	org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:579)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:700)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:808)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Unknown Source)
Note The full stack trace of the root cause is available in the server logs.

Apache Tomcat/8.5.42

                There was a similar one reported for Confluence docker image at https://jira.atlassian.com/browse/CONFSERVER-59318

                        dchevell Dave Chevell
                        5052ff715260 jayhding
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            dchevell Dave Chevell
                            5052ff715260 jayhding
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: