In <[EMAIL PROTECTED]>, Thorsten Franzke <[EMAIL PROTECTED]> writes:
> "Aengus" <[EMAIL PROTECTED]> wrote:
>
> > No you don't - if 401 was treated as a success, you'd get 2 "successful"
> > requests for that item. If you look closely at your log files, you see
> > that every time a 401 response code is sent, the item is requested again
> > immediately afterwards - the first time generates a 401, which causes the
> > browser to send the request a second time, but with authentication
> > information.
>
> Yes I do. Strange as it sounds -and I don't like to dicuss the usefulness of
> this, it isn't useful and it doesn't make any sense, but I am not the one to
> decide this- our internal server is configured in such a way that the
> respective 200 coming out of a 401 are NOT recorded.
> Again, I think that the way how our server is setup does not make any sense,
> but I cannot influence that decision. According to your reply I assume that
> I will have to continue with what I did before (search&replace).
Something like
cat logfile | perl -p -n -e "s!(HTTP/1...) 401!$1 200!;" | analog
should work (and would be another nice application for the PREPROCESSFILTER I
proposed earlier :-))
--
Klaus Johannes Rusch
[EMAIL PROTECTED]
http://www.atmedia.net/KlausRusch/
+------------------------------------------------------------------------
| This is the analog-help mailing list. To unsubscribe from this
| mailing list, go to
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| List archives are available at
| http://www.mail-archive.com/[email protected]/
| http://lists.isite.net/listgate/analog-help/archives/
| http://www.tallylist.com/archives/index.cfm/mlist.7
+------------------------------------------------------------------------
