> > 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? > > Given that you're re-writing the logs anyway, I'd suggest > just "fixing" the error code. I don't think you'll find a > more satisfactory solution.
Thanks Aengus, I has hoping there was an easy to way to make a non-compliant analog binary to match my non-compliant logs - but if it's not easy then I'll just 's/202/404/g' or something like that. Cheers Julian. __________________________________________________ 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 +------------------------------------------------------------------------
