From: Carsten S. <ca...@co...> - 2004-04-24 21:48:11
|
Hi Jérôme! On Sat, Apr 24, 2004 at 11:17:24PM +0200, Jérôme Desquilbet wrote: > Today, something like http://somesite.info/i/ redirects to > http://somesite.info/i/index.yaws if index.yaws exists in /i/. > First question: is there a particular reason why it doesn't simply stay > http://somesite.info/i/ ("silently" trigerring /i/index.yaws) ? It used to. Klacke changed that during the last rehaul to avoid having duplicate cache entries for /i/ and /i/index.yaws. I did not particularly like that and said so :-) I changed it back for my site, but did so in a hurry, so I was not sure if it was correct and did not discuss it further here. Patch is attached. Klacke, should I commit? > And http://somesite.info/i/?somevar=someval also redirects to > http://somesite.info/i/index.yaws but the parameters are lost. > Second question: could it stay http://somesite.info/i/?somevar=someval > and simply (silently) trigger > http://somesite.info/i/index.yaws?somevar=someval ? I think http://carsten.codimi.de/test/ works the way you want it to. The index.yaws is <erl> out(A) -> {ehtml, {pre, [], f("~p", [A#arg.querydata])}}. </erl> Greetings, Carsten -- Carsten Schultz (2:38, 33:47), FB Mathematik, FU Berlin http://carsten.codimi.de/ PGP/GPG key on the pgp.net key servers, fingerprint on my home page. |