#3207: tracd uses wrong URL scheme when behind https proxy
------------------------------+---------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone:
Component: general | Version: 0.9.5
Severity: normal | Resolution:
Keywords: |
------------------------------+---------------------------------------------
Comment (by [EMAIL PROTECTED]):
I'm quite sure (see below); this is also what the footer on
https://trac.vistabella.de/annot/ says (the URL that I provided).
I took a look at the logfile that tracd produced when started without
`-d`. I don't know anything about HTTP proxying but at least from the
logfile it seems that tracd has no way of knowing whether the original
request was http or https (since it receices http and runs on port 8080
but must produce https). I therefore believe tracd must be told explicitly
what scheme to use. Maybe the problem could be solved on the Lighttp side
but I would prefer a tracd solution.
{{{
: ~; apt-cache show trac
Package: trac
Priority: optional
Section: web
Installed-Size: 1696
Maintainer: Jesus Climent <[EMAIL PROTECTED]>
Architecture: all
Version: 0.9.5-1
Depends: python (>= 2.3), python (<< 2.4), python-clearsilver (>= 0.9.3),
python-pysqlite2 | python-sqlite (>= 0.4.3) | python2.3-psycopg,
python2.3-subversion, subversion (>= 1.0.1)
Recommends: apache2 | httpd, python2.3-setuptools (>= 0.5a13)
Suggests: enscript, python-docutils, libapache2-mod-python
Filename: pool/main/t/trac/trac_0.9.5-1_all.deb
Size: 300480
MD5sum: 5e8e4447aaae043d590589662f9ae1a1
}}}
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/3207>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
