DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42027>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42027 ------- Additional Comments From [EMAIL PROTECTED] 2007-07-31 21:14 ------- I put some thoughts about refactoring options parsing at: http://segundo.ricilake.net/options.txt Maybe they're useful. I was trying to not be too clever, be explicit in invariants, and get the semantics reasonable (while allowing AP_INIT_ITERATE argument parsing). The semantics are not quite the same as current httpd: for one thing, it throws errors on certain constructions (Options +Foo -Bar Glitch) and for another thing it allows you to split up absolute options over various Options directives in the same block, so that: Options Foo Options Bar (in one block) is the same as: Options Foo Bar I'm not sure whether those are plausible changes, but it seems like it would be useful to have a single library which did httpd-options style handling in a consistent way. By the way, the current FileETags error can be reproduced if you have Options -Indexes in a block which is merged with a block containing: FileETag None (because OPT_INDEXES is the same value as ETAG_NONE). So, for example, putting the 'FileETag None' directive in a vhost, and the 'Options -Indexes' directive in a <Directory> section will probably trigger the error when the directory and the vhost are merged. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
