Gibbon obfuscates the URLs for resources by adding a random hash to the url, much in the same way other systems like Google generate ‘private’ urls that can still be shared. I would guess this behavior is necessary as some parts of the system allow public access to pages that can have resources in them, including Departments and Units. It is still important to ensure your system is configured with security in mind and does not allow directory-level indexing of the file system.
As a system admin though you can take certain steps to restrict all access to the uploads folder. For example, I use a variation of the following mod_rewrite code in the /uploads folder .htaccess file (Apache) to prevent access to particular filetypes:
`RewriteEngine on
RewriteCond %{HTTP_REFERER} !^https://gibbon\\.your-domain\\.com.*$ [NC]
RewriteRule .*\\.(wav|swf|jpg|jpeg|gif|png|bmp|pdf)$ - [F,NC,L]`
```
Hope this helps!
It this something that you feel could usefully be implemented into the core? What are the up and downsides? The installer could insert the domain name into it…
As per the Post Install & Server Config documents (scroll to the second last section of the page), it is important that you also turn off folder browsing on your web server, to prevent people peeking into /uploads via their browser.