Hi Eric!
> I am probably missing something obvious again but here's something that
> has me puzzled. I have a CGI program that executes for every URL
> starting with /akasha. But if I leave off the trailing slash, I get a
> redirect to the URL with a /. Ideally what should happen is it
> shouldn't matter if there's a trailing slash, it should just invoke the
> CGI and be done with it. normally this is not a problem when accessing
> pages but it is causing problems for CGI. It would really be nice to
> not have to remember to add that trailing /
>
> what am I missing?
>
> Directory /akasha {
> Handler cgi {
>
> GET /akasha HTTP/1.1
>
> HTTP/1.1 301 Moved Permanently
> Location: /akasha/
That is the expected behaviour. The directory entry specifies how
its contents should be treated, not the entry itself.
For example, imagine that your CGI replies with a redirection to
"thing.cgi?whatever=1". In this case the final URL will be:
/akasha/thing.cgi?whatever=1
however, if the server would manage the directory like its content,
as you are proposing, the final URL would be:
/thing.cgi?whatever=1
--
Greetings, alo.
http://www.alobbs.com
_______________________________________________
Cherokee mailing list
[email protected]
http://www.0x50.org/cgi-bin/mailman/listinfo/cherokee
