Edgewall Software

Changes between Version 1 and Version 40 of Ticket #2553


Ignore:
Timestamp:
Jun 6, 2008, 9:07:40 AM (11 years ago)
Author:
Christian Boos
Comment:

Summarizing current status of the issue, after marking #7307 as duplicate.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2553

    • Property Status assignedclosed
    • Property Cc jorge.vargas@… added
    • Property Priority normalhigh
    • Property Keywords mod_proxy patch apache mod_python added
    • Property Version 0.9.2devel
    • Property Milestone 0.9.40.10.4
    • Property Owner Christian Boos removed
    • Property Resolutionfixed
    • Property Severity normalmajor
  • Ticket #2553 – Description

    v1 v40  
    1 Running tracd through stunnel, I access trac via a https://url/trac.Everything works fine until I change something (confirm a wiki edit, add anew ticket, login, etc.) and the url forwards to http://url/trac insteadof https.To fix this, I changed the `self.scheme = 'http'` in TracHTTPRequest instandalone.py to `self.scheme='https'`. But I imagine this shouldautodetect in some way.
     1Running tracd through stunnel, I access trac via a https://url/trac. Everything works fine until I change something (confirm a wiki edit, add a new ticket, login, etc.) and the url forwards to http://url/trac instead of https.
     2
     3To fix this, I changed the `self.scheme = 'http'` in TracHTTPRequest in standalone.py to `self.scheme='https'`. But I imagine this should autodetect in some way.
     4
     5=== Status for this issue ===
     6
     7This is a problem affecting Trac up to and including 0.10.4.
     8
     9In current 0.10.5dev and 0.11dev (b1, b2, rc1), there's a new setting in the TracIni#trac-section, `use_base_url_for_redirect`: when set to ''true'', Trac will use the value set for `base_url` in the same .ini section as the actual target for the redirects, so  you can set it to `https://...` if you really have no other choices. See also #6013.
     10