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.


In reply to Re^5: RFC / Audit: Mojo Login Example by haj
in thread RFC / Audit: Mojo Login Example by haukex

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.