On 11/16/2011 5:06 PM, Stefan Fritsch wrote:
On Wednesday 16 November 2011, William A. Rowe Jr. wrote:
Will people be confused by a directive that does nothing when
placed in a named vhost? Or should this just be global-only and
forget about it? It would be nice to cripple this module, say,
for the intranet side of a server, and enable the overhead only on
the external side.
Currently, it's per phys-vhost. Many SSL directives also have no
effect in non-default named-vhost, therefore I don't think that
RequestReadTimeout makes things worse.
It would really be amazing if we could distinguish the current
vhost context as physical (al la first-of-many named) or a named
host (being at least the second instance).
