Content Security Policy for script-src in SharePoint 2019 Onpremise
I would like to check if anyone could access on the content-security-policy for SharePoint 2019 onpremise. My appscan has detected and mandated the use of CSP for frame-ancestors, object-src and script-src. I'm facing issue with script-src it seemed that it requires the use of 'unsafe-inline' and 'unsafe-eval' which the IT security team disagree. Is there any way to set script-src without the use of 'unsafe-inline' and 'unsafe-eval'? Here is my CSP: Content-Security-Policy: frame-ancestors 'self' https://domain.com/; object-src 'self' https://domain.com/ ; script-src 'self' 'unsafe-inline' 'unsafe-eval'
Back to the Basics - How Is SharePoint Utilizing IIS? Sites Stopped Still Work
Hello, Everybody. I'm somewhat new to SharePoint administration but for the past year and a half I've been deploying new sites and digging in to some more advanced aspects of the system. However, today I was surprised when one of my SharePoints sites that was in a stopped state in IIS continued to function. Then I tested on another site and got the same results. This made me realize I must be missing something about the SharePoint architecture and how it utilizes IIS. A few details... I have around 15 sites. Some are marked to require SNI, and some are not. All run on ports 80 and 443 with a redirect rule in place. The two sites I tested by stopping both require SNI. Why is it the site can continue to load for the clients when the site is stopped in IIS? What am I missing? Thank You, Ryan
404 error while accessing SP Server Site 2013
404 error while accessing SP Server Site 2013. This is an intermittent issue. We recently had a crypto attack on all servers hence everything was turned off. When everything was settled, we started the server, application pools, did IIS reset,reboot of server. however all users are still facing issues while accessing all the sharepoint sites. They are receiving: Server Error in '/' Application. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly. Can someone advise on this? thank you