https://redmine.lighttpd.net/https://redmine.lighttpd.net/favicon.ico?13667327412007-05-23T13:59:52Zlighty labsLighttpd - Feature #1194: Partial matching in mod_evhost patternshttps://redmine.lighttpd.net/issues/1194?journal_id=28602007-05-23T13:59:52ZAnonymous
<ul></ul><p>"This feature should make it easier .... to migrate into lighttpd" is what i meant anyway :)</p>
<p>-- Lfe</p> Lighttpd - Feature #1194: Partial matching in mod_evhost patternshttps://redmine.lighttpd.net/issues/1194?journal_id=28612007-05-25T12:09:32ZDaniel-Brandt
<ul></ul><p>This is a first stab at the requested functionality.</p>
<p>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.. =)</p> Lighttpd - Feature #1194: Partial matching in mod_evhost patternshttps://redmine.lighttpd.net/issues/1194?journal_id=28622008-08-27T22:44:38Zstbuehler
<ul></ul><p>- defect != enhancement<br /> - syntax not clear, %{2.1} instead of %2.1 would be better</p> Lighttpd - Feature #1194: Partial matching in mod_evhost patternshttps://redmine.lighttpd.net/issues/1194?journal_id=102882016-07-17T06:05:32Zgstrauss
<ul><li><strong>Assignee</strong> deleted (<del><i>jan</i></del>)</li></ul> Lighttpd - Feature #1194: Partial matching in mod_evhost patternshttps://redmine.lighttpd.net/issues/1194?journal_id=103032016-07-17T06:05:54Zgstrauss
<ul><li><strong>Target version</strong> deleted (<del><i>1.5.0</i></del>)</li></ul> Lighttpd - Feature #1194: Partial matching in mod_evhost patternshttps://redmine.lighttpd.net/issues/1194?journal_id=104982016-09-23T10:03:47Zgstrauss
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/10498/diff?detail_id=8966">diff</a>)</li></ul><blockquote>
<p>- syntax not clear, %{2.1} instead of %2.1 would be better</p>
</blockquote>
<p>Any subscribers interested in testing this out?</p>
<p>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 <em>and</em> require surrounding {}, then those migrating from Apache syntax would need to make simple, straightforward changes to surround those specifiers with curly brackets {}.</p> Lighttpd - Feature #1194: Partial matching in mod_evhost patternshttps://redmine.lighttpd.net/issues/1194?journal_id=105882016-10-20T18:25:05Zgstrauss
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Patch Pending</i></li><li><strong>Target version</strong> set to <i>1.4.43</i></li></ul><p>implemented requiring %{2.1} instead of %2.1</p> Lighttpd - Feature #1194: Partial matching in mod_evhost patternshttps://redmine.lighttpd.net/issues/1194?journal_id=105912016-10-20T18:30:11Zgstrauss
<ul><li><strong>Status</strong> changed from <i>Patch Pending</i> to <i>Fixed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="[mod_evhost] partial matching patterns (fixes #1194) "%%" "%_" "%x" "%{x.y}" where x and y are *..." href="https://redmine.lighttpd.net/projects/lighttpd/repository/14/revisions/a3bba43b301ff03200599d0cff6a04bfbc305909">a3bba43b301ff03200599d0cff6a04bfbc305909</a>.</p>