IIS 7 and Above
Unauthorized 401 on IIS 7.5
Last post Nov 12, 2018 07:03 AM by Emaborsa
Oct 31, 2018 07:13 AM|Emaborsa|LINK
I developed a WebService using WCF Data Services. Debugging it on my localhost using VS2017 (IIS 10) it works fine. Once deployed on the server,
GET and POST work fine, PUT/PATCH/DELETE give a 401 error. IIS Logs say 401.3
I tried to switch from Anonymous Authentication to Windows Authentication, did not help.
I'm quite sure the problem relies in the IIS settings, but I'm not able to fix it.
Nov 01, 2018 09:43 AM|Brando Zhang|LINK
According to your description, I guess your application pool identity may not have the enough permission modify the file.
I suggest you could follow below steps to modify the identity pool permission.
1.Right click the web application in the IIS and click edit permission
2.Click the security and find out the IIS application pool's name. About how to find the application pool name ,you could refer to this
3.Modify the permission.
Nov 02, 2018 10:04 AM|Emaborsa|LINK
I understand, but which file? It must be something regarding WCF, because I have other applications and all work fine. This application is the only one with WCF and only this has the 401.3 problem.
Nov 07, 2018 01:28 AM|Brando Zhang|LINK
I suggest you could firstly check the application folder's permission.
You could right click the application in the IIS console and select 'edit permissions'.
Besides, I suggest you could check your wcf application's method to check you have done something to modify the file.
Nov 07, 2018 07:34 AM|Emaborsa|LINK
Thanks, I know how to check and edit persmissions but I'am looking which file/folder.
However, why do I have this problem only on CORS calls?
Nov 09, 2018 05:30 AM|Brando Zhang|LINK
In my opinion, CORS has nothing related with the 401.
Are this special calls fired other method in WCF?
Nov 12, 2018 07:03 AM|Emaborsa|LINK
I know it is strange, but the problem is only on CORS calls for PATCH, PUT and DELETE verbs and they are blocked before it'd be possible to debug them. So the problem must be the IIS or the WCF.