Zachary Uram wrote:
I wish to use Apache 2.2 to limit where users may go. I wish to avert
the so-called "fishing" where a user sees:
(note that I will be using name based virtual hosts to host multiple
domains on the same physical server/same ip)
http://www.site.org/whatever/something.html and
http://www.site.org/whatever/something.html and tries to access
http://www.site.org/whatever/
I would like it on a directory basis, a file basis may be needed later
but not for now.
Which rule would you set to disable access? Rule based on IP for instance?
If a user tries to access a forbidd
I wish to use Apache 2.2 to limit where users may go. I wish to avert
the so-called "fishing" where a user sees:
(note that I will be using name based virtual hosts to host multiple
domains on the same physical server/same ip)
http://www.site.org/whatever/something.html and tries to access
http:/