Prefs Removal Proposal

[David Marshall]

On Sep 4, 2007, at 2:35 PM, Gervase Markham wrote:

> 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/
>
> Then they can have http://bugzilla.foo.com/ redirect to http:// 
> secure.foo.com/bugzilla/ , and/or DNS alias bugzilla.foo.com to  
> secure.foo.com.
>
>

It's a false savings to get rid of sslbase if some users must  
reconfigure Apache.  If that also includes an actual redirection  
being sent back to the browser, that's even worse.

It is likely that someone out there has a set of circumstances in  
which he needs urlbase & sslbase to be entirely different and for  
whom Apache reconfiguration is not feasible.

Pushing things like this off to Apache for the sake of getting rid of  
a parameter is discourteous to say the least.