Apache and the trailing slash

lowbatt · Tux's lil' helper Joined: 13 Jul 2002 Posts: 83

I know this has been asked before. I've done google searches and forum searches but I can never seem to get a answer that I can get a grasp on how to fix it.

My question is how do you go about fixin a web site so you dont have to have the trailing slash EX www.bob.com/forum/ <--- that slash

I've read you can do it with the mod_dir modules ( set to load in my apache but it makes no diff) but nothing says if you need to do something special to make those work

I've read a Articale that says how to do it with mod_rewrite and with .htaccess files but I can seem to get that working at all. Seems apache ignores my .htaccess files.

So I'm looking for a guide on a simple way to fix this problem. Weither someone just types on up in this post or links to one that has good direction either works. I'm just tired of no being able to figgure this out.

All help is greatly appechiated and thank ahead of time!
_________________
Information is pure. Take a knife, for example. You can use it to cut up vegetables, butter your bread, etc. Or you can use it as a weapon. The way in which information exists in its many forms leaves for us the decision how to use it. - Maynard -TOOL

OdinsDream · Veteran Joined: 01 Jun 2002 Posts: 1057

What exactly is the problem you're having? I've never run across problems whether the slash is used or not, and I've got a fairly standard configuration Apache running right now.

These both lead to the same place:

lowbatt · Tux's lil' helper Joined: 13 Jul 2002 Posts: 83

well i finaly figgured it out. It was because i did not have the servername set in my config file.

_________________
Information is pure. Take a knife, for example. You can use it to cut up vegetables, butter your bread, etc. Or you can use it as a weapon. The way in which information exists in its many forms leaves for us the decision how to use it. - Maynard -TOOL

mglauche · Posted: Mon Oct 21, 2002 8:54 am Post subject:

To help u understand the problem :

http://foo.bar.com/somewhere is no vaild URL. Apache uses its internal rewriting to transform it into a valid one. but as u noticed, if you don't set the servername correctly, it can come to http://some.other.server/somewhere/ , which usually will cause a 404er

Usually the apache sends a "30x" response to the client about the missing "/"