I am getting below error post upgrade: 7.2.5
scenario 2 : Already present and still issues persists. but don't know whats that scenario 1. Please elaborate.
I did the following testing:
Added following below in server.xml: < Connector port="8080"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000"
enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true"/>
and when I hit http://ipaddress:8080... everything is working perfectly.
but when I edit in the following way in server.xmml: by adding proxy its showing the same error which I am getting in application access tab while adding the existing groups.
<Connector port="28080"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000"
enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true" scheme="https" proxyName="develop.qa.ampf.com" proxyPort="443"/>
So that mean, its proxy error. Please suggest the next steps
Ok, thanks for response. I degraded to 7.2.4 now. but still that issue persists.
and in apache I don't see such
Header unset Etag FileETag none in apache to enable as well. Please suggest.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Should be covered by http://httpd.apache.org/docs/2.4/mod/core.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Depends on the version and type of apache you're using. The docs for it will tell you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please, read the docs. It's in there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Scenario 1 is a mis-configuration in your apache server. You'll need to fix that. It's not a JIRA server setting, it's apache.
And what Vasiliy said - you need to think about reverting to a supported version, or at least prepare to upgrade as soon as a supported higher version is available.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.