URL:
<http://gna.org/support/?func=detailitem&item_id=1002>
Summary: Using a different domain for https doesn't work
Project: Savane
Submitted by: angelo
Submitted on: Wednesday 03/15/2006 at 20:03
Category: Installation/Configuration
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Release:
_______________________________________________________
Details:
I set up mydomain.com as my server, and then I set up secure.mydomain.com as
my https server. My apache setup redirects all https requests to
secure.mydomain.com, so https://mydomain.com/something/something redirects to
https://secure.mydomain.com/something/something
Consequently when I login to savane using and check the box that says to keep
using SSL after login, some pages redirect indefinitely back and forth between
https://mydomain.com and https://secure.mydomain.com
If Savane is configured to use secure.mydomain.com as the https server (as
per the configuration script written by yeupou), it should try to use this
domain name for all https request, and not use https://mydomain.com
Please ask any questions if I can clarify what's going on.
_______________________________________________________
Reply to this item at:
<http://gna.org/support/?func=detailitem&item_id=1002>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Savane-doc-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-doc-dev
