Chrome Developer Tools - more info on 401 (unauthorized) error?

In my Chrome dev tools I am getting the following error:

POST https://api.local.dealersocket.com/api/permissions 401 (Unauthorized)
angular.js:12011 XHR finished loading: POST "https://api.local.dealersocket.com/api/permissions".

Screenshot:

How can I get more info on this error?

I should have access to anything I need since it is our development team working on it. I just want to get more information so I can ask the right person the right questions. In other words, can Chrome Dev Tools provide more information?

Google Chrome OSWeb Development

Last Comment

Tom Knowlton

8/22/2022 - Mon

Dan McFadden

10/25/2016

An HTTP Error 401 is straight forward, the credentials you are hitting that API with, have not been granted access to the request resource.

To quote wikipedia:

401 Unauthorized (RFC 7235)
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.[33] 401 semantically means "unauthenticated",[34] i.e. the user does not have the necessary credentials.

Note: Some sites issue HTTP 401 when an IP address is banned from the website (usually the website domain) and that specific address is refused permission to access a website.

Link: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

Dan

Tom Knowlton

10/25/2016

ASKER

Dan:

That is a great response and is good information.

Can the Chrome Dev Tools provide even more information about the error in the Console I am asking about? Not about the nature of 401 errors, but rather I am asking if there is more information available via the Dev Tools interface itself?

I am sorry if I am not being clear. I am speaking more to the usage of the Dev Tools to investigate the errors that are reported rather than a definition of what a 401 error is.

ASKER CERTIFIED SOLUTION

Dan McFadden

10/25/2016

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

GET A PERSONALIZED SOLUTION

Ask your own question & get feedback from real experts

Find out why thousands trust the EE community with their toughest problems.

Tom Knowlton

10/25/2016

ASKER

"Not really... the HTTP Error codes are telling all that is required to fix the issue. To be clear, the definition of the 401 is the information that you need to report to whomever manages that endpoint."

I did some thinking about it, and I think you are right. The question becomes, "Who manages the black box that is this endpoint?" - who can explain to me why I am not able to authenticate, given my current credentials?

Thank you for your comments and time spent helping me with this.

This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.

rwheeler23

Dan McFadden

10/27/2016

I would speak with the system administrators or whomever manages the server.

Dan

Tom Knowlton

10/27/2016

ASKER

Agreed!

I think I can actually take a look at the source code, and even debug it. I'll have to look into it. We're not actively developing in the environment, this is all setup and configuration issues I am experiencing. But anywho - I'm happy with the answer I got. Thanks again!

Tom