Well, yes, plain text logging is fine. Apache and nginx log files are machine-readable. There is a RFC for the meaning of status codes, and LogFileFormat together with the server's documentation provide information about the fields you can expect.
But that's not enough: The typical form-based login will result in a redirection for both success (to whatever the application decides, probably just back to the page which caused a redirect to the login form in the first place) and failure (back to login). Frontend servers also don't log information from POST requests. Therefore, it is up to the application to provide the login name and the result. "Make the log entries machine-readable" doesn't imply a particular format, but rather: document how a log collector software can interpret your entries.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|