400 Bad Request

Question

Ramsudhakar Vedula_ylt3wg · Answer

jira.conf (Apache) ServerName m Include /etc/httpd/ssl/ddd.dd.include LimitRequestFieldSize 65536 LimitRequestLine 65536 LimitRequestFields 200 UseCanonicalName Off ServerAdmin webmaster@localhost ProxyRequests Off ProxyPreserveHost On ProxyTimeout 300 AllowEncodedSlashes NoDecode # Dont proxy the loadbalancer alive request ProxyPass /default.aspx ! Order deny,allow Allow from all RequestHeader set X-Forwarded-Proto "https" RequestHeader set X-Forwarded-Port "443" # To disable access and show maintenance message comment next 2 lines ProxyPass / http://localhost:8080/ nocanon ProxyPassReverse / http://localhost:8080/ on the tomcat server.xml " connectionTimeout="20000" redirectPort="8443" maxThreads="150" minSpareThreads="25" disableUploadTimeout="true" bindOnInit="false" enableLookups="false" acceptCount="100" URIEncoding="UTF-8" maxHttpHeaderSize="65536" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" proxyName="jira.oii.oceaneering.com" proxyPort="443"> Above are our current settings. Any suggested values?

Marc -Devoteam- · Answer

Hi @Paul Norrod

Welcome to the community.

As your tags on the post display that this is relating a DC instance, look at the log files on the server Jira is running on.

If oyu can't contact your Jira admin or the local IT department to help out.

Arkadiusz Wroblewski · Answer

Hi and welcome to the Community @Paul Norrod

The "400 Bad Request Request Header Or Cookie Too Large" message from nginx is the key detail here. It usually means that either Jira or the reverse proxy sitting in front of it is hitting a limit on the size of the headers or cookies your browser is sending. Since GitHub is a perfectly valid host for the plugin, the problem is likely with the request size rather than your Git configuration.

I’d suggest testing this in an incognito window first to see if that clears it up. If it works, you’re probably dealing with "cookie bloat" from your SSO or a browser extension that's stuffing too much data into your headers. If it still fails, your Jira admin will likely need to adjust the "maxHttpHeaderSize"  in the Tomcat or Nginx settings. It looks like Jigit is just passing along a low-level infrastructure error, so focusing on those server limits is your best bet.