Prefs Removal Proposal

Joel Peshkin bugreport at peshkin.net
Tue Sep 4 20:27:14 UTC 2007


John Beranek wrote:
> Let's reverse that. Let's say that the site's SSL server is
>
> https://secure.foo.com/
>
> and they only have an SSL certificate for secure.foo.com
>
> they wouldn't want to have to have Bugzilla live at
> http://secure.foo.com/ but rather have, say,
>
> https://secure.foo.com/bugzilla/
>
> and
>
> http://bugzilla.foo.com/
>
> John.
>
>   

The other way to deal with some of these uncommon prefs would be to 
combine them.

For example, if URLBASE is "http://bugzilla.foo.com/" and SSL is 
enabled, then SSLBASE is "https://bugzilla.foo.com/"

If, on the other hand URLBASE is set to "http://bugzilla.foo.com/  
https://secure.foo.com/bugzilla/", (a list), then URLBASE and SSL BASE 
differ by more than just the protocol field.

This would prevent adding extra fields for rare configurations at the 
expense of making it a bit trickier for the few who need the less common 
configuration.

I suspect that some fo the shadowdb parameters could be combined into a 
one-liner as well.




More information about the developers mailing list