That choice depends on your own site and what's most convenient for you.
You can rewrite either one from
but by default, anything without an extension will send your server looking for a directory and then for the index.whatever file in that directory. If they don't find it, some servers will then proceed to Option B, looking for a file with that name. It depends on whether a particular mod is present and enabled, but to be safe you'd better spend some time with your .htaccess.
Which is a different forum ;)
8:21 pm on Jul 15, 2011 (gmt 0)
We wouldn't changing the programming language any time soon. @lucy; with a server load perspective; better off being direct instead of having .com/keyword/ correct?
8:31 pm on Jul 15, 2011 (gmt 0)
Use a trailing slash ONLY if the URL is for a folder or for the index page in a folder.
Extensionless URLs for pages do not have a trailing slash.
9:24 pm on Jul 15, 2011 (gmt 0)
with a server load perspective; better off being direct instead of having .com/keyword/ correct?
I think your post overlapped g1 because I am tolerably certain he would have said to refer to the Index file as /keyword/ rather than write it out explicitly as /keyword/index.whatever
The reason is probably buried in the Apache docs somewhere.
10:05 pm on Jul 15, 2011 (gmt 0)
Never link to a named index page as a URL. It's Duplicate Content. Link to the canonical URL (ending with a trailing slash) instead. It also causes problems when you change the technology that runs the site.