Re: configuring lighttpd proxy for standalone roundup server

Hi Dave:

In message <CAETHaKrYDAUDkD4vHJ+XaD2fN5Lj8PtrOicH2Z2ysz0g58_d5w@mail.gmail.com>
,
Dave Bender writes:
>  I changed the config.ini to say https://example.com/trackers/example

Good 8-).

>I also changed my lighttpd proxy to the following:
>
>       $HTTP["host"] =~ "(^|\.)example\.com$" {
>
>                proxy.header = (
>                        "map-urlpath" => ( "/tracker/example/" => "/" )
>                )
>
>                proxy.server = (
>                        "/tracker" => (("host" => "127.0.0.1", "port" => 10220))
>                )
>
>        }

Bad 8-|).

>I can now properly activate the password reset.....

Success.

> However now I get a very strange path translation:
>
>This is the path I get in the email:
>
> https://example.com/tracker/example/user?@template=forgotten&@action=passrst&otk=McEezI3tJjZ7dsG5RpIO6Xe0fHg2OJP1

Which is correct.

>However, when I try to access that link, I get a 404:
>
>Error response
>
>Error code: 404
>
>Message: /user/?@template=forgotten&@action=passrst&otk=McEezI3tJjZ7dsG5RpIO6Xe0fHg2OJP1.
>
>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

The /example path is critical.

Can you recall what you read in our documentation that made you think
you should remove '/example/'?

You can use one roundup-server to serve multiple trackers. E.G.

   roundup-server ... support=/path/to/support/tracker/home \
                      internalit=/path/to/internalIT/tracker/home \
                      sales=/path/to/sales/tracker/home

there is no default tracker. The tracker name (in your case example)
is required to be passed to roundup-server.

>These are the log entries:
>
>127.0.0.1 - - [16/Apr/2023 15:14:58] "GET
>/user?@template=forgotten&@action=passrst&otk=McEezI3tJjZ7dsG5RpIO6Xe0fHg2OJP1
>HTTP/1.1" 301 -
>127.0.0.1 - - [16/Apr/2023 15:14:58] code 404, message
>/user/?@template=forgotten&@action=passrst&otk=McEezI3tJjZ7dsG5RpIO6Xe0fHg2OJP1
>127.0.0.1 - - [16/Apr/2023 15:14:58] "GET
>/user/?@template=forgotten&@action=passrst&otk=McEezI3tJjZ7dsG5RpIO6Xe0fHg2OJP1
>HTTP/1.1" 404 -

Yup, they are consistent with your rewrite rule since you are
stripping the '/example' tracker component/name.

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

Have a great day.
--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.