>Totally agree. In fact, I think there may be other cases where AS 3.4 >doesn't log Bad Request errors that are internally generated by AS. I >have had users do screen shots of Bad Request, yet I can't find them >in my logs. Could be stupidity on my part...dunno yet. > >Jim
I can confirm that uncaught errors will result in a connection that is not logged. And when I examine the logs of the reverse proxy master (aolserver running nsvhr), you can see the connections there that don't appear in an aolserver whose connection generated an error.) If I recall that's because access logging itself is implemented as a just another filter and the filter logic is such that an error in any filter results in the rest of the filters being skipped. It might be a good thing to have "finally" filters, that are run no matter what, and I wouldn't mind seeing finer grain control over which filter runs before which other filters (not just what phase they run in.) (As an aside, there is other information that may not get logged. As an example, anyone who returns their content with ns_write (I believe) and not ns_return, or not through an ADP page, will have erroneous logging of amount of content returned.) Jerry ======================================================== Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980 Berkeley, CA 94709 Fax: (877) 311-8688
