On Thu, Dec 02, 2004 at 10:22:49PM +0100, Claes Wikstrom wrote:
> We had some discussion a while ago about having an appmod named, ""
> or maybe "/". I seem to recall I had some really good argument
> against at the time but I can't recall it now.
> I would be fairly easy to allow that though. Why would you want
> this? ... Nahhh, never mind ... I can see reasons to have it.
Actually, I found out that I may not want to have this ;-) I had not
thought about having a non-virtual directory for images.
I now have all (virtual) html pages under /content.yaws/some/path/
(yes, although I do not like to have the yaws extension there, I like
to have the file recompiled automatically after changing it.) and
images under /images/. I do not like that particularly, but it's ok.
I might get rid of the content.yaws by using rewriting. Still I would
like to have more options at the rewriting stage, like returning a 404
directly. I may be using yssi to include yaws files under /raw/ anf
would not want the user to be allowed to access these directly. All
of this can be done, but some things somehow seem hacky. Maybe anyone
has a better way of structuring a server like this?
Carsten Schultz (2:38, 33:47), FB Mathematik, FU Berlin
PGP/GPG key on the pgp.net key servers,=20
fingerprint on my home page.