You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Noel J. Bergman (JIRA)" <ji...@apache.org> on 2006/01/07 17:13:21 UTC
[jira] Closed: (INFRA-661) JIRA should detect HTTPS access and stop
redirecting to plaintext
[ http://issues.apache.org/jira/browse/INFRA-661?page=all ]
Noel J. Bergman closed INFRA-661:
---------------------------------
Resolution: Fixed
We upgraded Tomcat to 5.5.15, installed APR under /usr/local/apr-install, compiled and configured the new APR-based native code support for tomcat.
See: http://tomcat.apache.org/tomcat-5.5-doc/apr.html
This should eliminate the limited connectiity problem, which resulted in HTTP 503 errors, due to workers not being able to establsh a connection to tomcat.
> JIRA should detect HTTPS access and stop redirecting to plaintext
> -----------------------------------------------------------------
>
> Key: INFRA-661
> URL: http://issues.apache.org/jira/browse/INFRA-661
> Project: Infrastructure
> Type: Bug
> Components: JIRA
> Environment: Ajax, JIRA http interface behind httpd 2.2.0 mod_proxy
> Reporter: Sander Temme
> Assignee: Noel J. Bergman
>
> We now have a certificate and SSL vhost configured on issues.apache.org. However, when browsing JIRA, it frequently redirects the user to plaintext http. This is undesirable as it forces the user out of the cosy SSL security blanket.
> Does JIRA have a switch that can be flicked to make it respect incoming plaintext access? For instance, can it be configured to work behind an external SSL offload appliance? Turning this on may force plaintext users to SSL but that bothers me less than the reverse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira