Well, the server will never serve the 403 page because your site allows everyone to access everything. Unless you actually set a flag in the server telling it to deny directory browsing or setup security authentication on the server, the client will always be able to view the directory listing. If you were hosting this website on your own computer, and thus using IIS or Apache, I could tell you where to go to configure these options.
However, the situation you're in is difficult because you don't have access to the server, regardless of what type of server it is. Therefore, one of two possibilities exist for you. 1) your host was savvy enough to realize that customers might want to turn this feature off, so somewhere in your configuration software they've buried an option to do this. 2) They haven't provided you with a way to do this, so you'll have to contact them and see if they'll manually set it up for you.
One hack that may work for you is to simple place a default page in every folder. Most servers are configured to first look for a default.htm or default.html page whenever a client omits a page. For example, say your site is normally accessed like this:
Now, say you want to keep people from browsing /theinsider folder. Like so:
If you place a default.htm or default.html page in /theinsider folder, then the above URL would cause the server to first look for default.htm, and since it's there, the server would send them that page instead of a directory listing. It's not the same thing as throwing the 403 error, but it prevents a directory listing.
Of course, that assumes your host's server is configured to act that way. IIS does this by default.
![[monkey]](/data/assets/smilies/monkey.gif "[monkey] [monkey]")
Edward