Hot answers tagged 401
6
Ok, there are APIs to support everything you're tyring to do, NEVER DIRECTLY EDIT THE web.config!!!!!!!
Follow these easy steps:
Package your custom error pages into a solution.
Hey, if you're doing the 401 you might want to add a couple of others to support access requests too ;)
Deploy the pages to {SP_Root}\Tempates\Layouts\MyErrorPages\ using a ...
4
Error 401 is for Unauthorized Access (or Access Denied). In a SharePoint site, "Access Denied" is managed at two levels - IIS and SharePoint.
The web.config changes you did are meant for IIS. As "access denied" inside SharePoint site is managed by SharePoint, for IIS there is no 401 and hence no redirection.
To set custom 401 page for a SharePoint site, ...
2
I have finally pinned it down. It turned out to be the feature of SharePoint's REST.
I needed to take UI language into consideration!
For instance, in case of en-us locale the REST query should look like this:
?$filter=endswith(Path,'FolderName')
But in ru-ru it becomes:
?$filter=endswith(Путь,'FolderName')
Moreover, you need to escape Russian ...
2
This sounds a lot like you are hitting the notorious NTLM Double Hop Problem and I'm sorry to say that there is no way around it aside from changing your authentication to Claims or Kerberos. Neither of which should be taken lightly.
If your code runs on the one of the machines in the SharePoint farm you are attempting to interact with, then you can ...
2
I imagine the reason is because SharePoint deals with authorisation, not authentication. You won't get SharePoint's access denied page as that is presented in cases where the users is authenticated but not allowed to see the requested resource (i.e. not authorised).
As for a resolution, I imagine you would need to modify the Web app web.config file. This ...
Only top voted, non community-wiki answers of a minimum length are eligible
