Serve content from a non root url directory

[rgl@…]

Allows you to configure tracd to serve trac environments inside a subdirectory, eg:

​http://example.com/trac/project

instead of:

​http://example.com/project

To do this, launch tracd with the argument: —base-path /trac

[rgl@…]

patch that implements this enhancement

[Matthew Good]

What's the justification for this? If the Trac projects are served from a sub-URL then there will be no page at the root, which would be very confusing.

If you can provide some reasons for doing this then the ticket could be reopened, but I can't see what setup would require this.

[rgl@…]

To have tracd sit behind a proxy (under any subdirectory) we need tracd to do this. eg: how do you make trac appear to the user at ​http://example.com/projects/myproject? with this patch you can.

[coderanger]

Look at the ProxyPass and ProxyPassReverse for Apache. I am sure there are similar directives for other servers.

[rgl@…]

coderanger, and why you think I don't known that? FYI, it does not work:

  ProxyPass /trac http://localhost:9090/

Then access using:

  http://localhost/trac/myproject

You will see the trac page, but all links returned by tracd are without the "/trac" prefix, eg:

  http://localhost/myproject/roadmap
  http://localhost/myproject/report
  ...

Also note, that in lighttpd (as of v1.4.11), its not possible to do the equivalent of ProxyPassReverse (and that only works with HTTP headers, not the contents of pages), nor its possible to map arbitrary paths, eg: the equivalent of apache

  ProxyPass /trac http://localhost:9090/

In lighttpd, will proxy to ​http://localhost:9090/trac/ and not ​http://localhost:9090/, because its not possible to specify the target directory.

So, please, fix this problem before next release!

[Jonas Borgström]

Fixed in r3050. Thanks!

[rgl@…]

Missing authentication patch

[rgl@…]

Ops, I missed the authentication part too. See the second attached file.

[Christopher Lenz]

Second patch applied in [3053]. Thanks!