enterprise-support team mailing list archive

[James Page <820936@xxxxxxxxxxxxxxxxxx>]

Switching "<Virtualhost *:80>" to "<Virtualhost _default_:80>" does not
make the default site configuration pickup global rewrite rule
definitions - see
http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#vhosts.

Going with option 2 (removing virtual host definition altogether) really
breaks the concept of sites-available and sites-enabled so I don't think
we should take that route.

Option 1 might be feasible - however I don't think that including all of
the conf.d directory within the VirtualHost definition is correct so it
would need a separate 'global rewrites' directory.

We would also need to bear in mind that mod_rewrite is not enabled by
default so maybe rewrite configuration should be treated as a
customization rather than part of the base installation.  Whatever we do
we should do it in-conjunction with Debian as changing default
behaviour/configuration could break alot of stuff.

Marking as 'Opinion' as merits further discussion.



** Changed in: apache2 (Ubuntu)
       Status: In Progress => Opinion

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to apache2 in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/820936

Title:
  Virtual server setup breaks Rewrite Rules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/820936/+subscriptions