Prefs Removal Proposal
kevin.benton at amd.com
Tue Sep 4 22:52:23 UTC 2007
> 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.
Okay - I have to ask - what is the real advantage of making Bugzilla
"less" configurable than it has been previously? There seems to be
enough people out there that would really not like to see urlbase and
sslbase removed from Bugzilla.
I can accept that some might say that there are too many parameters to
configure. For those in that camp, I suggest adding another parameter
configuration layer - basic and advanced. Those who need to tune
certain things that are not commonly accessed can head for advanced.
Those who are just getting started with Bugzilla will want to use basic
and leave the rest alone.
What am I missing?
MySQL DBA #5739
Senior Software Developer
MSS Silicon Design Engineering
Advanced Micro Devices
2950 E Harmony Rd
Fort Collins, CO 80528
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information. Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices. This
communication is for the intended recipient(s) only. If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.
More information about the developers