Mailing List Archive: Cherokee: dev

Issue 566 in cherokee: cherokee should parse config rules with regexs

Index | Next | Previous | View Threaded

codesite-noreply at google

Sep 7, 2009, 3:34 PM

Post #1 of 2 (349 views)
Permalink

Issue 566 in cherokee: cherokee should parse config rules with regexs

Status: New
Owner: ----

New issue 566 by ergomus: cherokee should parse config rules with regexs
http://code.google.com/p/cherokee/issues/detail?id=566

Problem:

server!bind!1!port=80 <-- this fails,

Solution: Possible regex to avoid this: [\w\d\!_]+[ \t]*=[ \t]*[\w\d\!_]+
proposed by alo :)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

cherokee at googlecode

May 9, 2010, 12:58 PM

Post #2 of 2 (157 views)
Permalink

Re: Issue 566 in cherokee: cherokee should parse config rules with regexs [In reply to]

Updates:
Status: WontFix
Labels: Type-Enhancement Priority-Low Component-Logic Usability

Comment #1 on issue 566 by ste...@konink.de: cherokee should parse config
rules with regexs
http://code.google.com/p/cherokee/issues/detail?id=566

Currently the configuration is in a fixed file format that should not be
edited by
hand. While the Cherokee Summit we have discussed other (better readable)
fileformats
to write the config in.

If you have discussions please send them on the mailinglist. Relaxing the
configuration parsing (or even making it more optimal since it has two
spaces less) is
ofcourse an option.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads