Prev: Changing IIS port number
Next: Unable to Bind IP/start website
From: Pravin Kumar on 30 Dec 2009 05:28
I have observed bunch of 401.1 and 401.3 errors, on investigating further I
noticed that for 99% of the times, for every 401.1 there's a 200 status code
logged in the IIS logs.
I took a pie chart in Indihiang Web log analyzer and noticed that there are
48% of 401 status codes. Is this something I should feel concerned about?
This application in question is external facing and we haven't had any
escalations from our customers .

Any help/suggestions in this regard is highly appreciated


Thanks,
Pravin

From: Dan on 30 Dec 2009 08:51

"Pravin Kumar" <pravin_skumar(a)hotmail.com> wrote in message
news:F22C92FD-802E-4F6C-B531-BB93015BFA81(a)microsoft.com...
> I have observed bunch of 401.1 and 401.3 errors, on investigating further
> I noticed that for 99% of the times, for every 401.1 there's a 200 status
> code logged in the IIS logs.
> I took a pie chart in Indihiang Web log analyzer and noticed that there
> are 48% of 401 status codes. Is this something I should feel concerned
> about? This application in question is external facing and we haven't had
> any escalations from our customers .
>
> Any help/suggestions in this regard is highly appreciated
>
>
> Thanks,
> Pravin

401 is the code sent to the browser to tell it that it needs to
authenticate. You'll then see a 200 if the browser then sends the request
again with the appropriate user credentials (either cached, or the user
types them in). Assuming that your sites use authentication rather than
handle anonymous requests then this os perfectly normal.

--
Dan

 | 
Pages: 1
Prev: Changing IIS port number
Next: Unable to Bind IP/start website