We had similar issue when using IIS as proxy in front of JIRA (and Confluence). The problem origin is from IIS Request Filtering module which deny access to some extensions and URL segments.
It's possible to remove this filter for a specific web application using the following commands at administrator command prompt:
appcmd set config "Web app name" /section:requestFiltering /-fileExtensions.[fileextension='.config']
appcmd set config
This document is from our internal KB :
I think what you'll want to do is edit the following file in your JIRA application:
And if you want these to be shown as plain text, more than likely you'll find the line that begins with:
Then build upon it. So mine by default looks like this:
text/plain asc txt patch log java
So yours may look like this:
text/plain asc txt patch log java config
Change this and restart JIRA, then hopefully you see them, rather than downloading them.
Hope this helps!
What does the atlassian-jira.log file say while you are trying to open the .config file from JIRA ticket. I have reproduced by saving a .config file and attached on JIRA 7.0.5 SQL Server.
Also let me know what version of JIRA you are running so I will try to replicate the issue.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs