Hi, At my work we use a Java based reporting system. This product logs to several logs including an access log that includes some very verbose information (across many many lines as well). I needed to get some more information on the behavior of this product. I eyeballed the log, wrote some perl to take the HTTP request and response dumps from the logs and rewrite them into common log format.
That was pretty straightforward, and I can now parse the logs with Analog 5.30 and get output written. The problem I have is that they use an HTTP response code of 202 to denote an error. I can see this because they have some plain text output as well that expands on the error. As per the HTTP RFC's, response 202 is classed as successful. So, without "cheating" and re-writing the 202 as a response code as an error in the 400 range when I take the raw logs and re-write them as common log format, is there a way to change analog's behavior to work with non-compliant response codes? I have googled, grepped the source, and read the documentation, but no joy. Thanks in advance, Julian. Julian Simpson [EMAIL PROTECTED] http://juliansimpson.is-a-geek.org __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
