1136669 - The urlbase parameter should be dynamic.

Status: RESOLVED DUPLICATE of bug 545410

(Bugzilla :: Administration, task)

Description

[Jochen Wiedmann]

We've got a Bugzilla server with multiple network interfaces. Depending on the user, one or the other interface (and, consequently, a different URL) will be used to reach Bugzilla.

As a consequence, we'd like to use different values for the urlbase parameter. For example, if the user is located in network 1, he will be using

   http://10.10.2.7/bugzilla

to reach Bugzilla, and that would be the proper value for urlbase. On the other hand, another user (located in network 2), would use

   http://192.168.9.4/bugzilla

A simple solution for us would be to configure urlbase as

   http://${SERVER_NAME}/bugzilla

and have Bugzilla evaluate that string by replacing ${SERVER_NAME} with $ENV{SERVER_NAME}.

I can provide a patch, if someone advices me what behaviour would be acceptable.

Comment 1

[:glob ✱]

sorry, but i think this use-case is too obscure to warrant taking into bugzilla.

however i'd welcome a patch that adds a hook at the end of Bugzilla::Config::read_param_file(). this should enable you to alter url_base from an extension.

Comment 2

[Frédéric Buclin]

Looks like a dupe of bug 545410, right? See also bug 500408.

Comment 3

[Frédéric Buclin]

(In reply to Byron Jones ‹:glob› from comment #1)
> however i'd welcome a patch that adds a hook at the end of
> Bugzilla::Config::read_param_file().

Is that really needed? Why cannot use the PROJECT env variable to do this?

Comment 4

[Jochen Wiedmann]

(In reply to Frédéric Buclin from comment #3)

> Is that really needed? Why cannot use the PROJECT env variable to do this?

I could use the PROJECT variable, if I had two Bugzilla instances. However, that's not my situation.
What I have, are two groups of users in two different networks, sharing a common Bugzilla instance.
The first group are the developers (in network 1), the other groups are the customers (in network 2).

Whatever, thanks for the suggestion to use a hook. I'll come up with a patch in bug 545410.