alexhenes wrote:Do you think it is dangerous to grant public write access to a folder that is available over the web app/_cache?
Interesting question!
It's not really "public" write access ... It just means that all "owners" of files under your website are allowed to write to that folder. If your server is setup correctly, there isn't any reason why there should be unknown "owners" under your website at all.
The main problem, is that many hosts assign one user for FTP uploads, and then the application PHP script becomes a separate user. Therefore, in order for the PHP script to write to a folder that has been created by FTP, you would need to set
write permissions also for "others"
(chmod 777):
If your server is setup in a modern smart way (like our hosting at
mediatemple), they have understood that that the FTP user should be the same user as the script that was uploaded by the FTP user. In these cases, you can set
write permissions for only the "owner"
(chmod 755) of the script. Often, you would not even have to set permissions in the first place, because 755 would be default.
If I was you, I would go ahead and try the above! X3 checks if the cache folder
iswriteable when opening a page, so if it doesn't work, you will get a notification message instead of seeing the website. If it does work, your website will "just work" like before. Good for you! Bravo to your host!
alexhenes wrote:The folks who host my server have major reservations.
I may be a bit judgmental here, but these server folks often know stuff like the above, yet they do not take this into account when making functional hosting. Try the above, and if chmod 755 works for you, then applause to your hosting. If 755 does not work, then I would like to ask your host how they can have reservations about chmod 777 if that is the only way for an application script to write data to a folder?