• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.5.2, 2.6 M2, 2.6
    • 2.5
    • User Interface
    • None
    • Linux, Sun Java 1.6, Tomcat 6.0.24, Chrome 4.0.302, Firefox 3.5.1, IE 8.0.6001.18702

      A clean WAR installation of Bamboo, using the express install option, creates an unusable dashboard for Chrome/Firefox users.

        1. catalina.out
          333 kB
        2. chrome.png
          chrome.png
          64 kB
        3. chrome-bamboo.zip
          132 kB
        4. context.xml
          0.1 kB
        5. explorer.png
          explorer.png
          71 kB
        6. firefox.png
          firefox.png
          52 kB
        7. firefox-bamboo.zip
          131 kB
        8. iexplorer-bamboo.zip
          131 kB
        9. localhost_access_log.2010-01-26.txt
          6 kB
        10. server.xml
          1.0 kB

            [BAM-5247] Bamboo is broken in chrome/firefox

            Krystian Brazulewicz added a comment - - edited
            Problem replication

            I was able to replicate the problem.
            While executed from unexploded WAR, Bamboo cannot read properly mime-types file and then serves CSS files as "Content-Type: application/octet-stream"

            $ curl --head http://localhost:8080/s/1712/1/1.0/_/download/batch/bamboo.web.resources:mainStyles/bamboo.web.resources:mainStyles.css
            HTTP/1.1 200 OK
            Server: Apache-Coyote/1.1
            Expires: Mon, 27 Jan 2020 10:36:14 GMT
            Cache-Control: max-age=315360000000
            Cache-Control: public
            Last-Modified: Fri, 29 Jan 2010 10:26:30 GMT
            ETag: "1264760790000"
            Content-Type: application/octet-stream
            Content-Length: 95165
            Date: Fri, 29 Jan 2010 10:36:14 GMT
            

            BTW. I gave you the wrong path to the CSS to validate.

            Solution

            The temporary solution is to use unpackWAR="true" for Bamboo context. The final solution is of course fixing the bug in Bamboo which is my current assignment.

            Krystian Brazulewicz added a comment - - edited Problem replication I was able to replicate the problem. While executed from unexploded WAR, Bamboo cannot read properly mime-types file and then serves CSS files as "Content-Type: application/octet-stream" $ curl --head http://localhost:8080/s/1712/1/1.0/_/download/batch/bamboo.web.resources:mainStyles/bamboo.web.resources:mainStyles.css HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Expires: Mon, 27 Jan 2020 10:36:14 GMT Cache-Control: max-age=315360000000 Cache-Control: public Last-Modified: Fri, 29 Jan 2010 10:26:30 GMT ETag: "1264760790000" Content-Type: application/octet-stream Content-Length: 95165 Date: Fri, 29 Jan 2010 10:36:14 GMT BTW. I gave you the wrong path to the CSS to validate. Solution The temporary solution is to use unpackWAR="true" for Bamboo context. The final solution is of course fixing the bug in Bamboo which is my current assignment.

            I am quite sure there are no proxies between my windows and this host.

            From my windows:

            C:\>curl --head http://pro246.xiv:8080/s/1711/1/_/styles/main.css
            HTTP/1.1 200 OK
            Server: Apache-Coyote/1.1
            Expires: Sun, 26 Jan 2020 13:22:39 GMT
            Cache-Control: max-age=315360000000
            Cache-Control: public
            Accept-Ranges: bytes
            ETag: W/"32199-1262082870000"
            Last-Modified: Tue, 29 Dec 2009 10:34:30 GMT
            Content-Type: text/css
            Content-Length: 32199
            Date: Thu, 28 Jan 2010 13:22:39 GMT
            
            
            C:\>curl --head http://pro246.xiv:8080/s/1711/1/_/styles/global-static.css
            HTTP/1.1 200 OK
            Server: Apache-Coyote/1.1
            Expires: Sun, 26 Jan 2020 13:22:39 GMT
            Cache-Control: max-age=315360000000
            Cache-Control: public
            Accept-Ranges: bytes
            ETag: W/"43901-1262082870000"
            Last-Modified: Tue, 29 Dec 2009 10:34:30 GMT
            Content-Type: text/css
            Content-Length: 43901
            Date: Thu, 28 Jan 2010 13:22:39 GMT
            

            From the pro246.xiv server itself:

            zevgeny@pro246:~()$ curl --head http://127.0.0.1:8080/s/1711/1/_/styles/main.css
            HTTP/1.1 200 OK
            Server: Apache-Coyote/1.1
            Expires: Sun, 26 Jan 2020 13:22:20 GMT
            Cache-Control: max-age=315360000000
            Cache-Control: public
            Accept-Ranges: bytes
            ETag: W/"32199-1262082870000"
            Last-Modified: Tue, 29 Dec 2009 10:34:30 GMT
            Content-Type: text/css
            Content-Length: 32199
            Date: Thu, 28 Jan 2010 13:22:20 GMT
            
            zevgeny@pro246:~()$ curl --head http://127.0.0.1:8080/s/1711/1/_/styles/global-static.css
            HTTP/1.1 200 OK
            Server: Apache-Coyote/1.1
            Expires: Sun, 26 Jan 2020 13:22:27 GMT
            Cache-Control: max-age=315360000000
            Cache-Control: public
            Accept-Ranges: bytes
            ETag: W/"43901-1262082870000"
            Last-Modified: Tue, 29 Dec 2009 10:34:30 GMT
            Content-Type: text/css
            Content-Length: 43901
            Date: Thu, 28 Jan 2010 13:22:27 GMT
            

            ( Using pro246.xiv:8080 as the hostname in this case gives exactly the same result. )

            Evgeny Zislis added a comment - I am quite sure there are no proxies between my windows and this host. From my windows: C:\>curl --head http: //pro246.xiv:8080/s/1711/1/_/styles/main.css HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Expires: Sun, 26 Jan 2020 13:22:39 GMT Cache-Control: max-age=315360000000 Cache-Control: public Accept-Ranges: bytes ETag: W/ "32199-1262082870000" Last-Modified: Tue, 29 Dec 2009 10:34:30 GMT Content-Type: text/css Content-Length: 32199 Date: Thu, 28 Jan 2010 13:22:39 GMT C:\>curl --head http: //pro246.xiv:8080/s/1711/1/_/styles/global- static .css HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Expires: Sun, 26 Jan 2020 13:22:39 GMT Cache-Control: max-age=315360000000 Cache-Control: public Accept-Ranges: bytes ETag: W/ "43901-1262082870000" Last-Modified: Tue, 29 Dec 2009 10:34:30 GMT Content-Type: text/css Content-Length: 43901 Date: Thu, 28 Jan 2010 13:22:39 GMT From the pro246.xiv server itself: zevgeny@pro246:~()$ curl --head http: //127.0.0.1:8080/s/1711/1/_/styles/main.css HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Expires: Sun, 26 Jan 2020 13:22:20 GMT Cache-Control: max-age=315360000000 Cache-Control: public Accept-Ranges: bytes ETag: W/ "32199-1262082870000" Last-Modified: Tue, 29 Dec 2009 10:34:30 GMT Content-Type: text/css Content-Length: 32199 Date: Thu, 28 Jan 2010 13:22:20 GMT zevgeny@pro246:~()$ curl --head http: //127.0.0.1:8080/s/1711/1/_/styles/global- static .css HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Expires: Sun, 26 Jan 2020 13:22:27 GMT Cache-Control: max-age=315360000000 Cache-Control: public Accept-Ranges: bytes ETag: W/ "43901-1262082870000" Last-Modified: Tue, 29 Dec 2009 10:34:30 GMT Content-Type: text/css Content-Length: 43901 Date: Thu, 28 Jan 2010 13:22:27 GMT ( Using pro246.xiv:8080 as the hostname in this case gives exactly the same result. )

            Evgeny

            Saved pages load correctly in all browsers (except CSS-defined background images). But I'm concerned about this error in the logs:

            2010-01-26 15:37:39,734 ERROR [main] [BambooContentTypeResolver] Failed to initialise the servlet's config file
            java.lang.NullPointerException
            	at java.io.File.<init>(File.java:222)
            	at com.atlassian.bamboo.plugin.servlet.BambooContentTypeResolver.loadMimeTypesFromConfigurationFile(BambooContentTypeResolver.java:71)
            	at com.atlassian.bamboo.plugin.servlet.BambooContentTypeResolver.init(BambooContentTypeResolver.java:33)
            

            Can you please paste the result of the commands:

            curl --head http://pro246.xiv:8080/s/1711/1/_/styles/main.css
            curl --head http://pro246.xiv:8080/s/1711/1/_/styles/global-static.css
            

            Last but not least: can you please check if there's any HTTP proxy between your machine and the Bamboo server? It can be either configured in your browser or it could be a transparent proxy (which is probably known to your IT department).

            Krystian Brazulewicz added a comment - Evgeny Saved pages load correctly in all browsers (except CSS-defined background images). But I'm concerned about this error in the logs: 2010-01-26 15:37:39,734 ERROR [main] [BambooContentTypeResolver] Failed to initialise the servlet's config file java.lang.NullPointerException at java.io.File.<init>(File.java:222) at com.atlassian.bamboo.plugin.servlet.BambooContentTypeResolver.loadMimeTypesFromConfigurationFile(BambooContentTypeResolver.java:71) at com.atlassian.bamboo.plugin.servlet.BambooContentTypeResolver.init(BambooContentTypeResolver.java:33) Can you please paste the result of the commands: curl --head http://pro246.xiv:8080/s/1711/1/_/styles/main.css curl --head http://pro246.xiv:8080/s/1711/1/_/styles/global-static.css Last but not least: can you please check if there's any HTTP proxy between your machine and the Bamboo server? It can be either configured in your browser or it could be a transparent proxy (which is probably known to your IT department).

            When I saved the pages to my desktop from the various browsers, I also tried opening the html files (on the desktop) in chrome/firefox - and it looks better, some tabs still missing their background, but overall the layout seems better.

            Can add more screenshots if required.

            Evgeny Zislis added a comment - When I saved the pages to my desktop from the various browsers, I also tried opening the html files (on the desktop) in chrome/firefox - and it looks better, some tabs still missing their background, but overall the layout seems better. Can add more screenshots if required.

            Saved webpage+files from all 3 browsers.

            Evgeny Zislis added a comment - Saved webpage+files from all 3 browsers.

            Evgeny,

            can you please save the contents of Bamboo dashboard in all three browsers and attach it to this issue?

            Krystian Brazulewicz added a comment - Evgeny, can you please save the contents of Bamboo dashboard in all three browsers and attach it to this issue?

            I tried reloading the page multiple times, the Administration page is also broken in a similar way, as well as multiple other pages. The login screen for example is not affected and looks okay.

            I also tried reinstalling Bamboo altogether, even on several different servers for the course of the last couple of weeks.

            This was also an issue with Bamboo 2.4.2, and possibly 2.4 ... after an upgrade some months ago it became broken in Chrome/FF.

            I also tried to clean cookies, and use the Chrome incognito mode - to no avail.

            I have no web filtering software on my PC that I know of, and I also tried to access the server from other people laptops and desktops - all looking the same (broken) on all.

            If you require mode debugging, please tell me and I can trace it down - since its not only reproducible, but it actually just wont go away.

            Evgeny Zislis added a comment - I tried reloading the page multiple times, the Administration page is also broken in a similar way, as well as multiple other pages. The login screen for example is not affected and looks okay. I also tried reinstalling Bamboo altogether, even on several different servers for the course of the last couple of weeks. This was also an issue with Bamboo 2.4.2, and possibly 2.4 ... after an upgrade some months ago it became broken in Chrome/FF. I also tried to clean cookies, and use the Chrome incognito mode - to no avail. I have no web filtering software on my PC that I know of, and I also tried to access the server from other people laptops and desktops - all looking the same (broken) on all. If you require mode debugging, please tell me and I can trace it down - since its not only reproducible, but it actually just wont go away.

            AntonA added a comment -

            Evgeny,

            Could you let me know if this is still an issue for you?

            I believe if you refresh the browser the page will come back OK.

            If not, could you try restarting.

            Please let us know how you go. Depending on the symptoms we will know better where to look for a problem.

            AntonA added a comment - Evgeny, Could you let me know if this is still an issue for you? I believe if you refresh the browser the page will come back OK. If not, could you try restarting. Please let us know how you go. Depending on the symptoms we will know better where to look for a problem.

            AntonA added a comment -

            Please note that we do not support Chrome.

            The fact that it does not work on Firefox is a problem.

            AntonA added a comment - Please note that we do not support Chrome. The fact that it does not work on Firefox is a problem.

            The tomcat server.xml/context.xml are quite standard

            Evgeny Zislis added a comment - The tomcat server.xml/context.xml are quite standard

              kbrazulewicz Krystian Brazulewicz
              ba734941625d Evgeny Zislis
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 8h
                  8h