Follow-up Comment #7, sr #1002 (project savane):

No, I am also using domain.com.  Maybe I'm understanding the savane
installation incorrectly.  I'll try to be more clear:

Config:
Main site:  http://domain.com/savane/
(no brother site)
Secure site:  https://secure.domain.com/savane/

Problem:
The problem is when you choose to stay in SSL mode after logging in, a
project page tries to use 

https://domain.com/savane/projects/my_project

instead of

https://secure.domain.com/savane/projects/my_project

To be more specific, I will describe the behavior as I see it (in case I'm
missing something).

Scenario 1:
Apache is configured to redirect https requests to secure.domain.com (i.e.
https://domain.com/X/Y/Z redirects to https://secure.domain.com/X/Y/Z)
In this case it redirects back and forth until the limit of redirects

Scenario 2:
Apache is configured to treat all https domain names the same (i.e. the
certificate can be invalid for some domains)
In this case Savane always gives me https://domain.com/savane/projects/X. 
Even if I type into the address bar:
https://secure.domain.com/savane/projects/X Savane will redirect me to
https://domain.com/savane/projects/X




    _______________________________________________________

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

Répondre à