I printed the address "mywebsite.com/portraits" on my most recent postcard.

Now when I tried to access this page, I get a 404 error - page not found.

But it exists.

If I put in mywebsite.com/portraits.html, the page loads.

What do I have to do so people can access this page without typing the .hmtl at the end (which nobody does).

I guess I lost quite some business through this problem.

Thanks for your tips.

rename the file index.html and put it in a folder called portraits.

Are you on Linux platform? Then, you can use mod_rewrite to redirect.

http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html

RewriteCond %{REQUEST_URI} ^/portraits
RewriteRule ^(.*) /portraits.html    [L]

Originally Posted by chrishirst

rename the file index.html and put it in a folder called portraits.

I did that, and came to a very complex problem that for now I cannot solve.


What I did: I named the file index.html, and put it in the folder "portraits".


Now, when I go to the page www.mywebsite.com/portraits the file opens. And it's called exactly that.

But I cannot link from this page to any other page on my website. All links fail.

I tried to do ../ to get out of the folder to the next level, and then put the name of the page in that I wanted to link to.

Doesn't work.

I leave the ../ out, and it doesn't work, either.

The weirdest thing is, that when I enter my site through the main index page and access the portraits page, it has a different address.

Now it's called www.mywebsite.com/portraits/index.html.

Now all links work.

So, basically, with this method I can manage to land on that page, but I can't get out.

The weirdest thing: the malfunction seems to only happen when using Firefox on a Mac (maybe on Windows, too, but I couldn't test for that).

And the real URI is?

Doesn't it depend on what the webserver considers as the "default" document type? For M$ servers (aka IIS) it's usually default.asp, index.html, and index.html.

It sounds like the default document type is set to something other than index.html (if /portraits still isn't working).

This is so awkward. But what happened is that I fixed the problem, but forgot to refresh the browser.

Of course the browser went back to the old, bad code.

Once I had emptied the cache, everything worked.