On Thursday, 05. October 2006 17:17, [EMAIL PROTECTED] wrote: > On 4 Oct 2006 at 16:38, Also Sprach Jörg Walter: > > It's the problem of all redirects. Apache is no different. The solution > > is to try the just discussed way of suppressing the redirects, or to > > /-terminate the URL right from the start. > > I can't work out how to suppress a redirect. I have managed to get > a / terminate though. > > A redirect seems to happen when the url is > > http://domain.dom:8000/foo?fire=hot
Right, this is explained in the same mail that mentions 'Path ""' as solution. Unfortunately, I forgot to mention that that solution (and the other things I explained today) need the current developer code from SVN. So whatever I explained, it all applies to changes _after_ AxKit2-1.1 > http://domain.dom:8000/foo/?fire=hot > > Is the above a valid url? the / before the ? looks wrong. It's a perfectly valid URL. If you don't want to upgrade, that's the easiest way to go. > In the above case a redirect is a waste of time, isn't it? Right. The redirect is done because of the way AxKit2 handles <Location> blocks, and only in the current development code that behaviour can be changed. > What I've done to get round my problem is to have a > fixup hook. If the request is a POST, I save the params to cache. > If it's a get and we aren't about to redirect, i save the params to the > client param api. > Is this a valid way to do it? (the best way?) I strongly suggest to upgrade, or if you don't want to, to use URLs ending with "/" where needed. Both variants are much better than a caching solution. -- CU Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]