We recently updated our instance of Confluence to run SSL only, off port 8443. Since moving to the encrypted web traffic, I have several clients still using Windows XP, and subsequently are tied to IE 8, and they cannot open or download any attachments. I have had one of the affected users test from my machine running Windows 7 and IE 9 and they can access attachments without issue.
90% of the time in support this is due to a wrongly configured Base URL, be sure that it's filled in to the same URL you're accessing your application with. To change this, read the following documentation: Configuring the Server Base URL.
If that doesn't fix it, place these Valve elements in the Context element of conf/server.xml:
<Valve className="org.apache.catalina.authenticator.FormAuthenticator" securePagesWithPragma="false" /> <Valve className="org.apache.catalina.authenticator.NonLoginAuthenticator" securePagesWithPragma="false" />
Thank you for your response. I will make the change and see if that works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you tried adding those lines to the Context in the server.xml?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You would have to recycle the service :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have modified the base URL and added the VALVE elements in the Contect element of sever.xml.
I am awaiting a response from my users to see if the additions/modifications have resolved the issue.
Are these immediate changes or does a service need to be cycled?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After adding the elements to the server.xml, I received errors while running c:\confluence\bin\startup.bat. The system wouldn't start up. I commented them out and everything gets running again.
I am still awaiting feed back from my users, I will see where this goes from here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you. They do not match, in fact there is a server name listed in the URL rather than a full https DNS address. We use a non standard port, and the old HTTP port is listed rather than the new HTTPS port. I will make the change and see if that makes a difference.
Thank you for the response.
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.