Re: configuring lighttpd proxy for standalone roundup server

> However.....
>
> When I try to login, I am forwarded ton unexpected URL:
>
> The login request path is a POST to:
>
> /tracker/example
>
> which correctly resolves to /example
>
> However, I get a 302 to
>
> https://example.com/tracker/tracker/example
>
> As seen in the log.
>
> 127.0.0.1 - - [16/Apr/2023 12:54:06] "POST /movibus/ HTTP/1.1" 302 -
> 127.0.0.1 - - [16/Apr/2023 16:54:06] code 404, message /tracker/movibus/
> 127.0.0.1 - - [16/Apr/2023 16:54:06] "GET /tracker/movibus/ HTTP/1.1" 404 -
>
> Why is there an extra tracker inserted here?

I was able to answer my own question. I was trying to serve multiple
bugtrackers from a common URL prefix "/tracker" using proxy.header to
strip the common prefix out.
However, it seems lighttpd does more and compensates for this by modifying 302.

So I removed proxy.header and adjusted config.ini and proxy.server accordingly.
Now I am happy to just have one working bug tracker using this method,
though I am sure I can serve more with it.

Thanks,
Dave