Bug#386207: Please improve documentation
Hello Andras, I guess the problem is solved by linking against libpcre. I tried to reproduce your example with current version and it worked as expected: CheckURL ^/foo($|/): http://bla/foo - HTTP/1.1 404 Not Found http://bla/foo/- HTTP/1.1 404 Not Found http://bla/foo/bla - HTTP/1.1 404 Not Found http://bla/blafoo/ - HTTP/1.0 501 Not Implemented The 404 errors are ok, because there is no `foo' on the webserver. If you have no objection, I would like to close this bug. -- Kind Regards, Michael Mende http://www.menole.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386207: Please improve documentation
On Sun, May 04, 2008 at 12:49:31PM +0200, Michael Mende wrote: Hi, I guess the problem is solved by linking against libpcre. This is good news. I tried to reproduce your example with current version and it worked as expected: CheckURL ^/foo($|/): http://bla/foo - HTTP/1.1 404 Not Found http://bla/foo/- HTTP/1.1 404 Not Found http://bla/foo/bla - HTTP/1.1 404 Not Found http://bla/blafoo/ - HTTP/1.0 501 Not Implemented The 404 errors are ok, because there is no `foo' on the webserver. If you have no objection, I would like to close this bug. Fine with me, as long as the documentation says that perl compatible regular expressions can be used. I think a single sentence suffices. Andras -- Andras Korn korn at chardonnay.math.bme.hu http://chardonnay.math.bme.hu/~korn/ QOTD: After they make styrofoam, what do they ship it in? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386207: Please improve documentation
Package: pound Version: 2.0-1 Severity: minor Hi, currently, the documentation doesn't say what syntax is supported when specifying URL patterns. Based on the examples, it's a subset of POSIX regular expressions, but ^ and $ don't seem to work. It would be nice if extended regular expressions were properly supported, or, failing that, the documentation would at least say what is supposed to work and what isn't. Specifically, I tried CheckURL ^/foo($|/) But this didn't have the anticipated effect (/foo and /foo/ were equally refused). Also, under the Service heading, the man page says: URL pattern Match the incoming request. If a request fails to match than this service will be skipped and next one tried. If all services fail to match Pound returns an error. You may define multiple URL conditions per service. If no URL was defined then all requests match. It's not clear whether multiple URL conditions are evaluated in an AND or an OR manner, i.e. whether all must match or only one. Andras -- Andras Korn korn at chardonnay.math.bme.hu http://chardonnay.math.bme.hu/~korn/ QOTD: Time is a great teacher, but it kills all its pupils. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
