Project

General

Profile

Feature #1194

Partial matching in mod_evhost patterns

Added by Anonymous over 10 years ago. Updated about 1 year ago.

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

100%

Estimated time:
Missing in 1.5.x:

Description

mod_evhost currently doesn't support matching parts in avaliable patterns such as "%2.1". This feature should make it easier for larger and "older" setups of mass vhosting in style with {{{/var/www/%3.1/%3.2/%3/ => /var/www/t/e/test/}}}

For a more detailed description; see apache's mod_vhost_alias. Additionally - apache also accepts negative 'counting' - but i'd say it's a separate ticket.

-- Lfe

mod_evhost_dot_notation.patch (1.42 KB) mod_evhost_dot_notation.patch Patch for 1.4.x branch admin, 2007-05-25 12:03
evhost-1.5.patch (2.04 KB) evhost-1.5.patch dot additions patch for evhost in1.5 -- patrickdk Anonymous, 2007-05-25 19:33
mod-evhost_tests.patch (6.99 KB) mod-evhost_tests.patch Testcases for 1.4.x admin, 2007-05-28 14:58

Related issues

Has duplicate Feature #2049: VirtualDocumentroot accept partial parts from subdomains %3.1, %3.2, %3.3 etcDuplicate2009-08-11

Associated revisions

Revision a3bba43b (diff)
Added by gstrauss about 1 year ago

[mod_evhost] partial matching patterns (fixes #1194)

"%%" "%_" "%x" "%{x.y}" where x and y are single digit 0 - 9
and y is the 1-indexed position of a single char to add, similar to
http://httpd.apache.org/docs/2.4/mod/mod_vhost_alias.html
(but not supporting the entire Apache mod_vhost_alias syntax)

The lighttpd syntax for adding a single char at a give position requires
that the "%{x.y}" syntax, including the curly braces, which is different
from the Apache mod_vhost_alias syntax.

x-ref:
"Partial matching in mod_evhost patterns"
https://redmine.lighttpd.net/issues/1194

Revision 75040e99 (diff)
Added by gstrauss about 1 year ago

[mod_evhost] mod-evhost.t tests (#1194)

(thx Daniel-Brandt)

x-ref:
"Partial matching in mod_evhost patterns"
https://redmine.lighttpd.net/issues/1194

History

#1

Updated by Anonymous over 10 years ago

"This feature should make it easier .... to migrate into lighttpd" is what i meant anyway :)

-- Lfe

#2

Updated by Daniel-Brandt over 10 years ago

This is a first stab at the requested functionality.

This is written after spending about 20h reading through sourcecode and docs, so there might be stuff you want to change or make better.. at least it's a start.. =)

#3

Updated by stbuehler over 9 years ago

- defect != enhancement
- syntax not clear, %{2.1} instead of %2.1 would be better

#4

Updated by gstrauss over 1 year ago

  • Assignee deleted (jan)
#5

Updated by gstrauss over 1 year ago

  • Target version deleted (1.5.0)
#6

Updated by gstrauss about 1 year ago

  • Description updated (diff)

- syntax not clear, %{2.1} instead of %2.1 would be better

Any subscribers interested in testing this out?

Since there might possibly be existing usage of mod_evhost which uses literal dots and digits in the template, perhaps there should be a directive to enable this feature if we provide the syntax without {} (which is how Apache supports it). However, literal {} in the template is unlikely, so if we provide the functionality and require surrounding {}, then those migrating from Apache syntax would need to make simple, straightforward changes to surround those specifiers with curly brackets {}.

#7

Updated by gstrauss about 1 year ago

  • Status changed from New to Patch Pending
  • Target version set to 1.4.43

implemented requiring %{2.1} instead of %2.1

#8

Updated by gstrauss about 1 year ago

  • Status changed from Patch Pending to Fixed
  • % Done changed from 0 to 100

Also available in: Atom