Browse Remote Storage

[Barry]

So I finally got around to trying the remote storage with a secondary SFTP server as bulk storage. Perhaps I am missing something basic here.

Images upload and transfer to SFTP without issue. However, if I look at the path that image is served from I can then use that base URL to browse to ALL the images on that remote server...

Here is the flow.

Image is uploaded to clubwallpapers.com then transferred to storage.clubwallpapers.com

I browse said image at
http://storage.clubwallpapers.com/2016/10/23/MassiveHDWallpapaerDump1080p_122-dNzxHhi.md.jpg

From there, I can deduce that images are served from
http://storage.clubwallpapers.com/2016/10/23/

If I hit that URL, I can see all images (that were uploaded today). How do I stop people from browsing this page?

 

[Lastopp]

Go to the root folder and create a file called .htaccess and add Options -Indexes

 

[Rodolfo]

Chevereto doesn't touch that server at all regarding in how it serve those files. You only need to disallow those listings depending if you are using Apache or Nginx.

It is a somethings very simple, in Apache is an .htaccess file with the the following:

Options -Indexes

In Nginx is the following directive:

location / {
    autoindex off;
}

 

[Barry]

Go to the root folder and create a file called .htaccess and add Options -Indexes

Thanks - created an .htaccess file at the root of the webserver and added Options -Indexes.

I can still browse the contents.

 

[Lastopp]

Thanks - created an .htaccess file at the root of the webserver and added Options -Indexes.

I can still browse the contents.

Oh, I see. That rule only works for files in the root folder. If you want it to work for every folder on your server you should go to your Apache settings and remove indexes.

http://www.linuxscrew.com/2008/06/03/faq-how-to-disable-directory-browsing-in-apachehttpd/

 

[Rodolfo]

I can still browse the contents.

When that happens is usually because:

1. The virtualhost directive is either overriding or ignoring your .htaccess directives
2. Your .htaccess file has wrong permission mask or it isn't a valid .htaccess file

In some cases that directive could be in conflict with some cPanel indexing rules. Anyway, this is something that you should check with your hosting company. Like I said, is a totally common thing and maybe they just need an additional or even a different process to achieve it.

 

[Barry]

Oh, I see. That rule only works for files in the root folder. If you want it to work for every folder on your server you should go to your Apache settings and remove indexes.

http://www.linuxscrew.com/2008/06/03/faq-how-to-disable-directory-browsing-in-apachehttpd/

Thanks - needed to edit it at the httpd.conf level. Instead of -indexes, I needed to delete the word index.

Cheers,

 

[Rodolfo]

Glad you worked out

 

[Barry]

Glad you worked out

Awesome support as usual..