Re: configuring lighttpd proxy for standalone roundup server

Dave Bender <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.user
Message-ID <CAETHaKp8VOQNZ1fzpjsx-zO08MYrQqk4Tg1PKR-zjXHA8dAbLQ@mail.gmail.com>
Hi John

> >Error code explanation: 404 - Nothing matches the given URI.
>
> That's expected. You should be passing /example/... to the Roundup
> server.  Only /tracker/ should be stripped. By removing '/example/',
> you removed the component of the path that identifed the tracker. I
> assume you are running somehing like:
>
>    roundup-server ... example=/path/to/example/tracker/home

In my cmdline invocation, I had literally name=/....

I had seen

Usage: roundup-server [options] [name=tracker home]*

and not thought to change name=

>
> The /example path is critical.
>
> Can you recall what you read in our documentation that made you think
> you should remove '/example/'?

Mistaken experimentation on my part?

> Undo the change for lighttpd and this issue should go away.


The issue did go away and my password reset works as expected now.

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?

Appreciate your help so far. Every response you have given has helped
me make progress.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.