Received: (qmail 43034 invoked by uid 501); 24 Oct 2000 16:46:54 -0000 Message-Id: <20001024164654.43031.qmail@locus.apache.org> Date: 24 Oct 2000 16:46:54 -0000 From: John Andrea Reply-To: jandrea@satlantic.com To: submit@bugz.apache.org Subject: XSSI not fully documented X-Send-Pr-Version: 3.110 >Number: 6736 >Category: documentation >Synopsis: XSSI not fully documented >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: apache >Arrival-Date: Tue Oct 24 09:50:00 PDT 2000 >Closed-Date: Wed Oct 25 07:55:35 PDT 2000 >Last-Modified: Wed Oct 25 10:20:01 PDT 2000 >Originator: jandrea@satlantic.com >Release: 1.3.14 >Organization: >Environment: Unrelated. >Description: mod_include doesn't fully document XSSI directives (regular expressions for instance) even though this example document http://httpd.apache.org/docs/misc/custom_errordocs.html shows the use of regular expressions. >How-To-Repeat: Unrelated. >Fix: Write documentation. >Release-Note: >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: fanf State-Changed-When: Tue Oct 24 10:11:11 PDT 2000 State-Changed-Why: I don't see what the problem is -- regexps are documented to the extent that they are used. mod_include.html says: Compare string1 with string 2. If string2 has the form /string/ then it is compared as a regular expression. Regular expressions have the same syntax as those found in the Unix egrep command. From: John Andrea To: fanf@apache.org Cc: apbugs@apache.org Subject: Re: documentation/6736: XSSI not fully documented Date: Tue, 24 Oct 2000 14:28:15 -0300 >I don't see what the problem is -- regexps are documented to >the extent that they are used. mod_include.html says: > Compare string1 with string 2. If string2 has the form /string/ > then it is compared as a regular > expression. Regular expressions have the same syntax as those found > in the Unix egrep command. But it doesn't says that it uses egrep compliant expressions. Then there is a software bug which I'll report independantly, because "^" does not work. _______________________________________ John Andrea Satlantic Inc. Sys Admin 3295 Barrington St. jandrea@satlantic.com Halifax, NS Canada B3K 5X8 902-492-4780 Comment-Added-By: fanf Comment-Added-When: Tue Oct 24 12:04:32 PDT 2000 Comment-Added: I don't really understand what you are saying. The documentation quite clearly states that the regexp uses egrep syntax. As far as I can tell, ^ works as intended; there is however a syntax error in the custom_errordocs.html page. From: Tony Finch To: John Andrea Cc: apbugs@apache.org Subject: Re: documentation/6736: XSSI not fully documented Date: Wed, 25 Oct 2000 14:08:15 +0000 John Andrea wrote: > >However, all my tests (1.3.9, 1.3.14) show that > >always returns false, yet /\// and even /^./ both return true. >I assumed that "^" was not allowed and so wondered if the >allowed regex's needed to be documented. > >Now it looks like an expression parsing error. Though I find it hard to >believe that no-one else has ever attempted to match a hat slash. Use single quotes, not double quotes. Tony. -- en oeccget g mtcaa f.a.n.finch v spdlkishrhtewe y dot@dotat.at eatp o v eiti i d. fanf@covalent.net State-Changed-From-To: feedback-closed State-Changed-By: fanf State-Changed-When: Wed Oct 25 07:55:33 PDT 2000 State-Changed-Why: Problem should be resolved now. From: Tony Finch To: John Andrea Cc: Tony Finch , apbugs@apache.org Subject: Re: documentation/6736: XSSI not fully documented Date: Wed, 25 Oct 2000 17:14:22 +0000 John Andrea wrote: >Tony Finch wrote: >> >>Use single quotes, not double quotes. > >Then how about documenting that. It is documented in the mod_include documentation; you were copying some incorrect examples from custom_errordocs.html which I have fixed. Tony. -- en oeccget g mtcaa f.a.n.finch v spdlkishrhtewe y dot@dotat.at eatp o v eiti i d. fanf@covalent.net >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]