Clicking on Excel view gives the error message:

      Microsoft Excel cannot access the file 'https://sdev.sil.org/sdev/jira/secure/IssueNavigator.jspa?view=excel&tempMax=1000'. There are several possible reasons:

      ? The file name or path name does not exist.
      ? The file you're trying to open is being used by another program. Close the document in the other program, and try again.
      ? The name of the workbook you're trying to save is the same as the name of another document that is read-only. Try saving the workbook with a different name.

        1. atlassian-core-2.0.17.jar
          62 kB
        2. EncodingFilter-old.class
          3 kB
        3. JIRAEncodingFilter.class
          2 kB

            [JRASERVER-1738] Excel export over https doesn't work

            For the above comment refer to https://support.atlassian.com/browse/JSP-29635.

            Jonathan Costello [Atlassian] added a comment - For the above comment refer to https://support.atlassian.com/browse/JSP-29635 .

            We have applied the following configuration to our Jira environment's Apache server:

            <Location /jira>
                Header set Cache-Control "private, must-revalidate"
                Header unset Pragma
            </Location>
            
            <Location /jira/secure/attachment>
                Header unset Cache-Control
            </Location>
            

            I added the second <Location ...> section in order to maintain the headers which are currently set on attachments being delivered.

            This appears to be working with the correct behaviour.

            Jonathan Costello [Atlassian] added a comment - We have applied the following configuration to our Jira environment's Apache server: <Location /jira> Header set Cache-Control " private , must-revalidate" Header unset Pragma </Location> <Location /jira/secure/attachment> Header unset Cache-Control </Location> I added the second <Location ...> section in order to maintain the headers which are currently set on attachments being delivered. This appears to be working with the correct behaviour.

            AntonA added a comment -

            Resolving the issue.

            Bill, please let us know if it is working on your side.

            AntonA added a comment - Resolving the issue. Bill, please let us know if it is working on your side.

            Selders added a comment -

            Just have tested with latest Mozilla browser on Windows XP and that works. It also works on latest Linux Fedora with Netscape 7.0.1. So far it does not work when Mozilla is 1.3.1 on Redhat 9. It makes no difference to go to straight to tomcat or through the apache proxy. May be it is a problem with this specific version of Mozilla. I will do an upgrade somewhere this week.

            Based on these findings I must conclude that this issue is solved on your side. Our users are happy. For our linux users we have a good configuration now that will work. Thanks for the support.

            Selders added a comment - Just have tested with latest Mozilla browser on Windows XP and that works. It also works on latest Linux Fedora with Netscape 7.0.1. So far it does not work when Mozilla is 1.3.1 on Redhat 9. It makes no difference to go to straight to tomcat or through the apache proxy. May be it is a problem with this specific version of Mozilla. I will do an upgrade somewhere this week. Based on these findings I must conclude that this issue is solved on your side. Our users are happy. For our linux users we have a good configuration now that will work. Thanks for the support.

            Bart,

            We have performed extensive testing of the patched files running on Mozilla (Linuz) and IE (Windows) with Tomcat 4.x and Tomcat 5.0.19 (HTTPS) - and we have been unable to replicate the issue you described for Mozilla on Linux once the patched files have been applied.

            Can you describe your desktop environment in greater detail? (Mozilla version, etc.)

            Is it possible to access Tomcat directly in order to remove the proxy server from the equation?

            Thanks

            Keith Brophy added a comment - Bart, We have performed extensive testing of the patched files running on Mozilla (Linuz) and IE (Windows) with Tomcat 4.x and Tomcat 5.0.19 (HTTPS) - and we have been unable to replicate the issue you described for Mozilla on Linux once the patched files have been applied. Can you describe your desktop environment in greater detail? (Mozilla version, etc.) Is it possible to access Tomcat directly in order to remove the proxy server from the equation? Thanks

            Selders added a comment -

            I just have tested this issue once more with Internet Explorer 6.0028 on Windows 2000. I had no problems with downloading a MS word attachment over https. This was on a Jira system with the bugfix applied.

            After this fix Windows users are now able to download Excel reports over https as well. As described before there are only problems introduced for Linux users.

            For clarity: we use Jira 2.6.1/Tomcat/MySql on RedHat 9 as backend server, furthermore we use Apache 1.3.x web server running https as a proxy webserver.

            Selders added a comment - I just have tested this issue once more with Internet Explorer 6.0028 on Windows 2000. I had no problems with downloading a MS word attachment over https. This was on a Jira system with the bugfix applied. After this fix Windows users are now able to download Excel reports over https as well. As described before there are only problems introduced for Linux users. For clarity: we use Jira 2.6.1/Tomcat/MySql on RedHat 9 as backend server, furthermore we use Apache 1.3.x web server running https as a proxy webserver.

            Bill Lear added a comment -

            By the way, this did not in fact fix the Excel download problem.
            I tried clicking on the Excel view and it failed. I checked the dump of the headers and the no-cache header is still being set.

            Bill Lear added a comment - By the way, this did not in fact fix the Excel download problem. I tried clicking on the Excel view and it failed. I checked the dump of the headers and the no-cache header is still being set.

            Bill Lear added a comment -

            Yes. I was under the impression that this issue also covered the other problems with downloading under https. This is the issue into which Scott entered my concerns and to which he directed me for follow-up.

            Is there no fix in mind for the Microsoft attachment problem?

            Bill Lear added a comment - Yes. I was under the impression that this issue also covered the other problems with downloading under https. This is the issue into which Scott entered my concerns and to which he directed me for follow-up. Is there no fix in mind for the Microsoft attachment problem?

            AntonA added a comment -

            Bill,

            The fix was only meant to fix one URL - the excel export from Issue Navifator. Are you referring to downloading MS Word attachments over https?

            AntonA added a comment - Bill, The fix was only meant to fix one URL - the excel export from Issue Navifator. Are you referring to downloading MS Word attachments over https?

            Bill Lear added a comment -

            This is still broken under Tomcat 5.x. I enabled a dumper valve to check the headers. I moved the atlassian-core-2.0.15.jar out of the way and copied in atlassian-core-2.0.17.jar. I moved JIRAEncodingFilter.class and installed the new one. I restarted Tomcat. The dump shows the headers are still being set:

            2004-05-11 21:48:12 RequestDumperValve[Catalina]: header=Pragma=No-cache
            2004-05-11 21:48:12 RequestDumperValve[Catalina]: header=Cache-Control=no-cache

            Needless to say, the download does not work (this is for a Microsoft Word document, incidentally).

            We are getting frustrated here. I really do appreciate Atlassian's effort, but I have spent a lot of time pursuing this with nothing to show, and an annoyed VP of development poking me every week about getting this fixed.

            Bill Lear added a comment - This is still broken under Tomcat 5.x. I enabled a dumper valve to check the headers. I moved the atlassian-core-2.0.15.jar out of the way and copied in atlassian-core-2.0.17.jar. I moved JIRAEncodingFilter.class and installed the new one. I restarted Tomcat. The dump shows the headers are still being set: 2004-05-11 21:48:12 RequestDumperValve [Catalina] : header=Pragma=No-cache 2004-05-11 21:48:12 RequestDumperValve [Catalina] : header=Cache-Control=no-cache Needless to say, the download does not work (this is for a Microsoft Word document, incidentally). We are getting frustrated here. I really do appreciate Atlassian's effort, but I have spent a lot of time pursuing this with nothing to show, and an annoyed VP of development poking me every week about getting this fixed.

              anton@atlassian.com AntonA
              f984fdfaba0f Ed Kenschaft
              Affected customers:
              5 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: