Forum Discussion
Chrome & Edge Encounter 403 Forbidden Errors with SharePoint API Calls (e.g. People Picker)
The organization I support has a short history of having SharePoint 2016 site collections not work well with Chrome and Edge. JavaScript and out-of-the box API calls encounter 403 Forbidden when using Chrome or Edge. Internet Explorer 11 works fine.
While I have been able to resolve this issue in my development environment, engineering has been unable to do so in production. I'm not allowed access to production, so there is a lot of back and forth. For some of the production collections, with each collection having a separate app pool, Chrome and Edge work. For others they do not. Configuration management is not a strong suit for engineering.
As the subject indicates, the errors apply to some SharePoint features like the People Picker. I've not turned up much in this area. Does anyone have any experience or ideas?
Thanks.
- Hi Personally I have not encountered this issue in my 2016 farm but looks like other people are getting this error.
Please refer the below article where the REST API call throws the error.Let me know if this helps or we can troubleshoot it further.
https://sharepoint.stackexchange.com/questions/177350/rest-403-response-on-chrome-firefox-edge-but-not-ieAs I stated in the post, SharePoint's built-in, out-of-the-box features suffer from this issue and the issue does not exist in my development environment. I don't see this as a development issue, it is clearly something on the server side.
Thanks Thuyavan Ganesan for the Google Search.
