Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-11774

IE6 clients download spacer.gif from wrong URL many times

XMLWordPrintable

      If Confluence is set up without a context path, there will be a performance impact from requests being served for spacer.gif. This is a particularly large problem when the clients using Confluence are Internet Explorer 6.

      The primary problem is that the requests use the wrong URL and hit the (slightly expensive) 404 page:

      "GET /display/CONFEXT/undefined/images/border/spacer.gif HTTP/1.1" 404 40448 196468

      That's 40 KB download in a response that took 196 ms to generate. By contrast, a 200 response for this file serves 43 bytes in 2 ms and also gets caching headers returned so subsequent requests get a 304 response.

      "GET /images/border/spacer.gif HTTP/1.1" 200 43 1632

      The other related problem is that IE6 clients request this resource once per comment on a page, rather than once for the whole page.

            [CONFSERVER-11774] IE6 clients download spacer.gif from wrong URL many times

            David Taylor (Inactive) added a comment -

            Works fine. Might recommend looking at ways to abstract use of AlphaImageLoader to a single JS helper method in AJS, but not required for release.

            David Taylor (Inactive) added a comment - Works fine. Might recommend looking at ways to abstract use of AlphaImageLoader to a single JS helper method in AJS, but not required for release.

            Matt Ryall added a comment - - edited

            Chris B has a separate issue to dumb down the default 404 page, I believe. I think we're removing the space list from the 404 page entirely, making it almost completely static.

            Update: Mike, this is done but not committed yet. The relevant issue is linked, CONF-9050.

            Matt Ryall added a comment - - edited Chris B has a separate issue to dumb down the default 404 page, I believe. I think we're removing the space list from the 404 page entirely, making it almost completely static. Update: Mike, this is done but not committed yet. The relevant issue is linked, CONF-9050 .

            Mike Cannon-Brookes added a comment -

            Guys - I'm sure you've considered it, but could we simply have a basic 404 page for any image or CSS requests (which aren't going to visually seen by anyone anyway) across all our apps?

            Mike Cannon-Brookes added a comment - Guys - I'm sure you've considered it, but could we simply have a basic 404 page for any image or CSS requests (which aren't going to visually seen by anyone anyway) across all our apps?

              matt@atlassian.com Matt Ryall
              matt@atlassian.com Matt Ryall
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: