Forum Discussion
SharePoint as a pseudo web-server?
Hi all, I'm looking for opinions on using SharePoint as a pseudo web-server for a website.
For ~2 years now, we've been posting files/images/etc. to our website using SharePoint anonymous access links rather than our web server; this was done because we decided to allow distributed editing, and we saw SharePoint's document libraries as the only good way available to us at the time to protect the web editors from stumbling into posted documents that ought not be messed with. We hadn't had any critical problems, but there have been serious-ish issues I've noticed that make me question the wisdom of the move. For example, the nature of anonymous access links is such that they aren't endpoints, they're pathways--if an anonymous user tries to share the link of a document after they've viewed it, they are giving out the endpoint link, which nobody but our web editors would have access to. I didn't understand this when I implemented it, and while our users have never reported it to us as an issue, but it does happen now and then with our own organization's staff.
Any lessons learned about this approach would be greatly appreciated!
1 Reply
- Rob EllisBronze ContributorI would perhaps looking at using Flow to copy files from SharePoint to your web server - see https://flow.microsoft.com/en-us/connectors/shared_ftp/ftp/
You could put some conditions / workflow around it - e.g. if an item is 'approved', then copy it from SP to webserver, etc.