Make sure Anonymous access is enabled on IIS -> Authentication. But also right click on it, then click on Edit, and choose a domain\username and password. (With access to the physical folder of the application).
To answer your questions: How to deal with unauthorized requests? The way you described it is pretty much the recommended way for a RESTful service. As far as I can see there is absolutely nothing wrong with that. What WWW-Authenticate header should 401 responses supply? In general the WWW-Authenticate header tells the client what kind … Read more
By definition (see RFC 2616), the HTTP 302 response code is the redirect code. Without it, the location header may be ignored. However, you can send an HTTP 401 response and still display output. Instead of redirecting the user to an error page, you could simply write your content you want to send in the … Read more
Another way of keeping your video private is to change in the “Privacy / Settings” the option Only people with a password, to “Hide this video from Vimeo.com” and “Only on sites I choose”. The reason you might benefit from this is that you have control over the sites that can embed the video. You … Read more
You have to whitelist a domain specified in the hosts file in order for windows authentication to work: Click Start, click Run, type regedit, and then click OK. In Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters Right-click Parameters, click New, and then click DWORD (32-bit) Value. Type DisableStrictNameChecking and press ENTER. Double-click the DisableStrictNameChecking … Read more
this is possible with jQuery $.ajax() method $.ajax(serverUrl, { type: OutageViewModel.Id() == 0 ? “POST” : “PUT”, data: dataToSave, statusCode: { 200: function (response) { alert(‘1’); AfterSavedAll(); }, 201: function (response) { alert(‘1’); AfterSavedAll(); }, 400: function (response) { alert(‘1’); bootbox.alert(‘<span style=”color:Red;”>Error While Saving Outage Entry Please Check</span>’, function () { }); }, 404: function … Read more
If you want to use interceptors to handle 401 error here is code snippet. axios.interceptors.response.use(response => { return response; }, error => { if (error.response.status === 401) { //place your reentry code } return error; });
I realize this is an older post but I had the same error on IIS 8.5. Hopefully this can help another experiencing the same issue (I didn’t see my issue outlined in other questions with a similar title). Everything seemed set up correctly with the Application Pool Identity, but I continued to receive the error. … Read more
A clear explanation from Daniel Irvine [original link]: There’s a problem with 401 Unauthorized, the HTTP status code for authentication errors. And that’s just it: it’s for authentication, not authorization. Receiving a 401 response is the server telling you, “you aren’t authenticated–either not authenticated at all or authenticated incorrectly–but please reauthenticate and try again.” To … Read more