C
Cindy
Noticed something I don't understand. I have several webs on an Apache
server with FP extensions.
On one of the webs, I am able to remotely browse the contents of
subdirectories...like the /images directory...and see the directory
contents. On the other webs, I get the expected 404 error if I attempt to
do this.
I could not figure out what the difference is between the webs that makes
one vulnerable this way. I resolved it for now by putting an index.htm page
in each subdirectory to block access to directory contents, but what is the
key to getting this one web to make subdirectories unbrowsable for contents?
Thanks
server with FP extensions.
On one of the webs, I am able to remotely browse the contents of
subdirectories...like the /images directory...and see the directory
contents. On the other webs, I get the expected 404 error if I attempt to
do this.
I could not figure out what the difference is between the webs that makes
one vulnerable this way. I resolved it for now by putting an index.htm page
in each subdirectory to block access to directory contents, but what is the
key to getting this one web to make subdirectories unbrowsable for contents?
Thanks