Project

General

Profile

Bug #1588

(log pollution) mod_evhost is active even when there is no hostname specified in the request

Added by Anonymous almost 12 years ago. Updated over 11 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
mod_evhost
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

To reproduce:
1/ Declare a evhost.path-pattern, e.g.:
server.modules += ("mod_evhost")
evhost.path-pattern = "/var/www/%0/%3/htdocs/"
2/ Point your browser at the machine's ip adress, e.g. http://1.2.3.4/

Result:
Lighty displays the contents of server.document-root as expected, but mod_evhost tried to access a virtual host directory, leaving the following message in the system logs (with level == 'err'):
(mod_evhost.c.307) No such file or directory /var/www/3.4/2/htdocs/

Expected:
mod_evhost should be silent when no named host is passed in the request, and not build a virtual host document root from evhost.path-pattern (that is, simply defaulting to server.document-root)

As an alternative, since it does in fact properly fall-back to server.document-root, it should at least not log this message with a level as high as 'err' but use a lower level (such as 'debug').

-- julien.cayzac

#1

Updated by stbuehler almost 12 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

You are wrong; if you do not send a Host: header at all, mod_evhost does not trigger.

But most clients send the ip as Host: name, which is valid imho, and mod_evhost tries to work with that - i see nothing wrong with that.

#2

Updated by stbuehler over 11 years ago

  • Status changed from Fixed to Invalid

Also available in: Atom