Failed to load resource: the server responded with a status of 401 ()
See original GitHub issueI inserted utterances in my blog and it is working. But I got this 401 error in Chrome console.
POST https://api.utteranc.es/token 401
These are the lines where I got error, specifically this function r.apply(this, arguments);
Failed to load resource: the server responded with a status of 401 ()
Does anybody know why? Does this affect commenting functionality in any way?
"function" == typeof fetch && (fetch = e(fetch, (r = fetch,
function(t, e) {
var n = s(e)
, o = r.apply(this, arguments);
if (n) {
function u(t) {
c({
requestID: n,
statusCode: t && t.status
})
}
o.then(u).catch(u)
}
return o
}
)));
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Failed to load resource: the server responded with a status of ...
When servers respond with access denied message (401 Unauthorized access), it means that the anonymous IIS user account is unable to access ...
Read more >the server responded with a status of 401 (Unauthorized ...
The 401 Unauthorized Error is an HTTP status code error that represented the request sent by the client to the server that lacks...
Read more >401 Unauthorized - HTTP - MDN Web Docs
The HyperText Transfer Protocol (HTTP) 401 Unauthorized response status code indicates that the client request has not been completed ...
Read more >Failed to load resource: the server ... - Relativity Community
We found that this can be due to an issue with the browser caching. Clear your browser cache and try accessing Relativity again...
Read more >401 Unauthorized Error: What It Is and How to Fix It
The 401 Unauthorized Error is an HTTP response status code indicating that the client could not authenticate a request.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is an expected status/response. The client does a POST to /token to retrieve the user’s credentials/signed-in status. If the user is not signed in the service responds with a 401. Maybe I should make this a
204 no content
to avoid confusion.401 Unauthorized: The user did not provide authentication credentials, or was not authenticated.
Reference: https://developer.mozilla.org/zh-CN/docs/Web/HTTP/Status/401
There is no problem with the response status 401 and it is impossible to be more correct. Sometimes wrong means right. If verification is performed without verification information, verification will naturally fail.