Jira reverse proxy always reloads batch.js

Question

I have recently upgraded to JIRA 6.3.7 from the 5.x branch. We have always fronted JIRA with a reverse proxy to handle https and this was working correctly before upgrade.

With this new release, each page load is extremely slow and from examining the network logs for the files loaded we are seeing that the batch.js is continually reloaded. For some pages this can mean 2-3mb of javascript per page load and load times are upwards of minutes for some of our more remote users.

If we hit JIRA directly the batch.js is not reloaded after the first time and responds with 304 Not Modified, but with the reverse proxy it is always reloaded even though the headers are preserved. We have tried both Apache as recommended and Nginx but both suffer from this issue.

How can we configure the proxy not to reload batch.js unnecessarily?

unknown · Answer

I am having same issue. Not sure what is the cause here as it used to work before. I used different computers and networks but no luck. Can something be weird with my hotspot device or network location?

Victor Maslov · Answer

AFAIK browser rereads content if URL has query parameters. You have `?locale=en-US...`. I have them too in our JIRA and I would like to know how to disable that thing. Switching my user preferences locale to the "Default" one doesn't remove that parameter, but just changes the value.

Stephen Gargan · Answer

David,

Thanks for your response, looking at your headers I realized that my nginx version was very old. Funny that even with the latest Ubuntu it installs a 1.4.x version of nginx.

I upgraded and tried with both 1.6.2 and 1.7.5 and while the situation is a little better its still causing reloads of batch.js. If I reload the page immediately it will (mostly) come back 304, but if i move to another page e.g. view a ticket and go back it all gets reloaded again.

Headers for the call are as follows, other than being an admin it all looks pretty similar

Request URL:https://xxxxx/s/fe7311b0b64ff3d6a0d27479c6783010-T/en_USpqbwcm/6337/5/e313bcb3b8747471263026fce0cce706/_/download/contextbatch/js/greenhopper-rapid-non-gadget,atl.general,gh-rapid,jira.global/batch.js?locale=en-US&isAdmin=true

Request Method:GET

Status Code:200 OK

Request Headersview source

Accept:*/*

Accept-Encoding:gzip,deflate,sdch

Accept-Language:en-US,en;q=0.8

Cache-Control:max-age=0

Connection:keep-alive

Cookie:AJS.conglomerate.cookie=""; gh.i=%7B%7D; atlassian.xsrf.token=BOLG-9TGG-18S2-KRUC|39162d7764429d8154dde3963b9257637fd7df0c|lin; JSESSIONID=194CF9BF4CF8315FF29367604BBB79D2

Host:xxxxxx

Referer:https:/xxxxxx/secure/RapidBoard.jspa?rapidView=8&selectedIssue=HDPOKER-3074

User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.104 Safari/537.36

Query String Parametersview sourceview URL encoded

locale:en-US

isAdmin:true

Response Headersview source

Cache-Control:max-age=31536000

Cache-Control:public

Connection:keep-alive

Content-Type:application/javascript;charset=UTF-8

Date:Fri, 17 Oct 2014 14:20:26 GMT

ETag:"1413291246000"

Expires:Sat, 17 Oct 2015 14:20:26 GMT

Last-Modified:Tue, 14 Oct 2014 12:54:06 GMT

Server:nginx/1.6.2

Transfer-Encoding:chunked

X-AREQUESTID:860x44252x1

X-ASEN:SEN-2343805

X-ASESSIONID:ahuqs6

X-Content-Type-Options:nosniff

X-Seraph-LoginReason:OK

My nginx config looks like this

server {
 listen 443 ssl;
 server_name xxxxxx;
 ssl_certificate /opt/atlassian-jira-6.3.7-standalone/xx.crt;
 ssl_certificate_key /opt/atlassian-jira-6.3.7-standalone/xx.key;

client_max_body_size 10M;

location / {
 proxy_set_header X-Forwarded-Host $host;
 proxy_set_header X-Forwarded-Server $host;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_pass http://localhost:8080;
 proxy_redirect off;
 }
}
server {
 server_name xxxxxxx;
 listen 80;

location / {
 return 301 https://$server_name$request_uri;
 }
}

Anything Glaring stick out for you with this? Thanks for your help.