[SOLVED] Strange behaviour with apache virtualhost

miguelg · 04-17-2014, 06:39 PM

I've got Bugzilla set up as a virtualhost (see definition below) accessible only within a LAN that is behaving strangely. If I point the browser to bugzilla.daedalus, Bugzilla does not load up and instead I'm presented with the perl script (page doesn't render); it renders correctly if I navigate to daedalus instead though.

Why?

Code:

<VirtualHost *:80>
  ServerName bugzilla.daedalus
  ServerAdmin ****@gmail.com       # censored

  DocumentRoot /var/www/bugzilla-4.4.2

  <Directory /var/www/bugzilla-4.4.2>
    Options +Indexes +ExecCGI -MultiViews +SymLinksIfOwnerMatch +FollowSymLinks
    AllowOverride All
    Order allow,deny
    Allow from all
    AddHandler cgi-script .cgi .pl
  </Directory>
</VirtualHost>

Running Apache 2.4.6.

John VV · 04-17-2014, 07:13 PM

A bit of a different note

you might want to change this part

Quote:

AllowOverride All
Order allow,deny
Allow from all

that makes the folder open to the WHOLE wide world .Not just the lan but EVERYONE in the world

something like ---

Code:

Order deny,allow
Deny from all
Allow from 123.456.789.012

replace "123.456.789.012" with the address of the lan
see the Apache documents Vhost section
http://httpd.apache.org/docs/2.4/vhosts/

miguelg · 04-18-2014, 12:35 AM

John, many thanks for the pointer; it had completely eluded me!

Anyone has any idea why Apache is behaving in the manner I described in my OP?

John VV · 04-18-2014, 01:52 AM

is mod perl installed and turned on ?

a good test for that is the log gui awstats

miguelg · 04-18-2014, 03:35 AM

It is, yes. Got the following when querying apache's loaded modules:

Code:

$ a2query -m perl
perl (enabled by maintainer script)

miguelg · 04-19-2014, 08:38 AM

Bump!

Anybody has any more ideas?

miguelg · 04-24-2014, 02:41 PM

Sigh. The issue was being caused by the virtualhost's conf file not having a .conf extension. Apparently it's a new requirement introduced in Apache 2.4.

Note to developers: it could at least emit a warning, if not to stdout, at least to the server log!