DO NOT REPLY [Bug 31734] New: - request: a command-line argument to produce a machine-parsable list of configuration dirctves, similar to 'apache -L' output

[bu...@apache.org]

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=31734>.
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=31734

request: a command-line argument to produce a machine-parsable list of configuration dirctves, similar to 'apache -L' output

           Summary: request: a command-line argument to produce a machine-
                    parsable list of configuration dirctves, similar to
                    'apache -L' output
           Product: Apache httpd-1.3
           Version: 1.3.31
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: schamp@commonwerx.org


Hello. 
 
I'd been hoping to write some software that would need to know "which Apache 
configuration directives are not 'server config'-only directives?" 
 
I'd remembered that the Apache directives manual contains such "context" 
information. This is nice, for a human reader. 
 
'apache -L' also produces such information -- including (1) the configuration 
directive, and (2) a summary of the configuration contexts, in which the 
directive is valid -- but, this too is produced for a human reader. (Since it 
is produced with a systematic grammar, the 'apache -L' output should be 
parsable, too, but ... "there must be some other way") 
 
If there was a command-line argument (for the 'apache' command), which would 
produce something /like/ 'apache -L', but would produce it in a 
machine-parseable form (in a format, maybe, like that of "gpg --list-keys 
--with-colon") ... that should be immensely helpful. 
 
 
(Also, for directives such as <directory>, which must have a "closing 
delimiter": a reference to the appropriate "closing delimieter" could be 
included in the output, too, maybe) 
 
...and if the machine-parsable output would be produced, simply, as plain text 
-- nothing buried in XML -- then that should be ... very, very helpful. 
 
 
(This is needed for an open-source project, at the point of: Something to help 
a user/admin to manage configuration directives for 'virtual host' entities. I 
could say more about the particular project, but there isn't much to show for 
it, yet.) 
 
 
 
Thank you, sincerely

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org