Versions Compared

Old Version 4

changes.mady.by.user Jeff Turner

Saved on

compared with

New Version 5

changes.mady.by.user Jeff Turner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Excerpt

This page is for anyone who has been tempted to add files (e.g. js, css) into JIRA's atlassian-jira/ directory. It may come as a surprise, but JIRA suffers from the most basic of bugs: it doesn't serve static files correctly. More specifically, if Tomcat serves the file with gzip compression, the Content-Length: header is incorrectly set.

Note

This is now filed as a JIRA bug, 

Jira
serverAtlassian JIRA
serverId144880e9-a353-312f-9412-ed028e8166fa
keyJRASERVER-66932

 

Let's pick on jira.jboss.org for our demo, but you can use any public, non-Cloud JIRA instance fronted by Apache (not nginx, which seems to mask the problem). Try hitting https://jira.jboss.org/robots.txt. This loads, but hangs for 20 seconds.

...

  • Now you know why JIRA's 404 page always seems slow. I would file a bug, but Atlassian no longer accept bug reports on https://jira.atlassian.com, and filed as bug 
    Jira
    serverAtlassian JIRA
    serverId144880e9-a353-312f-9412-ed028e8166fa
    keyJRASERVER-66932
     indirectly via support request 
  • If you want to add custom Javascript, CSS or other non-image files to atlassian-jira, you can't rely on Tomcat to serve them. Better to serve the static files directly via your frontend webserver.

...