Forum Moderators: phranque

Message Too Old, No Replies

Apache Local Setup - not seeing my folder!

Missing folders when viewing localhost...

         

jeffreyhall

7:45 pm on Aug 22, 2006 (gmt 0)

10+ Year Member



Hi all -

Somewhat newbie here. I am trying to setup a test server on my local pc using XAMPP. I have it all installed and setup (I think correctly). Have a virtual host setup for the default XAMPP interface, and this works fine.

The problem I'm having is: I have another virtual host setup for my public_html folder (which I pulled from the production website) and Apache doesn't see it.

My localhost root is empty except for the XAMPP and public_html folders. When I go to localhost in FF or IE, it only lists the XAMPP folder.

When I go to my public_html virtual host, I get a server error. Anyone have any ideas?

FYI:
The public_html folder contains an oscommerce php website. there is a .htaccess file in it (not sure exactly what that is, but lots of people seem interested in them here!) and there are config.php files to point it all to mysql.

MySql seems to be setup correctly, so i don't think the issue is there.

Any help is GREATLY appreciated.... ->Jeff

jdMorgan

12:02 pm on Aug 23, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



> When I go to my public_html virtual host, I get a server error. Anyone have any ideas?

What error, specifically? Anything in the server error log file?

Jim

jeffreyhall

12:41 pm on Aug 23, 2006 (gmt 0)

10+ Year Member



Well, it looks like I fixed it. I removed the .htaccess file from the directory and *POOF!* it became visible and was able to access it thru it's virtual host name.

Now, I have no idea why this happened because I'm dumb about .htaccess files. If anyone wants to point me to some posts/info about it that would be helpful?

Cheers... -->jh

jdMorgan

1:22 pm on Aug 23, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Apache .htaccess file [httpd.apache.org]

The most likely cause of your problem is that the .htaccess file contained code to restrict access to the directory itself (as opposed to the files in that directory). This is usually done for security reasons -- to prevent people and search engine robots from fishing around in your directories for files you may not want them to find for various reasons.

Jim