Some URLs don't work through proxy (due to parameters in URL possibly)

[Ryan Duff]

I have Jira proxied through IIS, over HTTPS.  It works 99% of the time, but I've noticed a few situations where it doesn't:

1:  When first starting up the server, if I navigate to the site locally on the server, I get the graphical startup sequence showing the add-ins loading, etc.  However, when I nagivate through the proxy remotely, I get a blank screen with "The service is unavailable." text.  After the server fully loads, I can navigate to it through the proxy perfectly fine, and everything appears to work normally.

2:  I can create new issues using the Create button normally.  However, if I look up an issue through the search feature, navigate to that issue, and then press the Create button, I get the Jira loading spinner icon indefinitely.  The only difference between here, and when I can successfuly press Create within an issue, is that there are additional parameters in the address bar due to the recent search, ie:

https://devtoolssandbox.championsway.internal/jira/browse/PMDEV-22856

vs

https://devtoolssandbox.championsway.internal/jira/browse/PMDEV-22856?jql=

I noticed that during startup, the URL has parameters as well:

https://devtoolssandbox.championsway.internal/jira/startup.jsp?returnTo=%2Fdefault.jsp

Then, I found this warning in the Jira log, which seems to be related, but I don't know how to address it from here:

04-May-2017 12:12:31.744 WARNING [ajp-nio-8009-exec-2] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://devtoolssandbox.championsway.internal/jira/rest/issueNav/1/issueTable/stable, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

Can anyone offer any insight?  Thank you.

[edwin vasquez]

Hello @Ryan Duff 

were you able to figure this out? I've experience this recently as well.