DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7741>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7741 some directives-contexts in online-documentation are not uptodate. Summary: some directives-contexts in online-documentation are not uptodate. Product: Apache httpd-1.3 Version: 1.3.23 Platform: Other URL: http://http://httpd.apache.org/docs/mod/core.html#limitr equestbody etc OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: core AssignedTo: bugs@httpd.apache.org ReportedBy: [EMAIL PROTECTED] CC: bugs@httpd.apache.org Sorry if i'm reposting this! According to online documentation, you can use each directive only in the specified context,or it won't work. But the context information for following directives seems uncomplete: -LimitRequestFields [docu says:] Context: server config [docu should say:] Context: server config, virtual host -LimitRequestFieldsize [dito] -LimitRequestLine [dito] -Same for all directives around KeepAlive. All above do work correctly also when set per virtualhost. -Include [docu says:] Context: server config [docu should at least say:] server config, directory As for ServerPath, documentation says Context: virtual host; but it seems possible to set this in server config. if this doesn't make sense, a parser "..is not allowed here" message into errorlog would be nice. online-docu says: "The directive is only allowed within the designated context; if you try to use it elsewhere, you'll get a configuration error that will either prevent the server from handling requests in that context correctly, or will keep the server from operating at all -- i.e., the server won't even start."
