they are executed as provided, so in the default way with no modification, the problem is with tomcat5 and jetty6, but I think that it's with all other containers.
What really mess up things is providing dojoSource via asset, because ";jsessionid=...." is attached, and that dojo gives back a lot of 404. Shure there is a workaround on this providing a custom delegate, but it seems to me that providing a dojoSource the way I have described so far doesn't work. What do you think ? On 4/17/07, Martino Piccinato <[EMAIL PROTECTED]> wrote:
the first time you hit a page url rewriting is enabled because the servlet container has no way to tell whether you support cookies or not (you don't send any cookie header as you still don't have a cookie). See my other reply about what could be the real problem (not url rewriting but a web server that does not know how to interpret rewritten url). Which servelet container/web server are you using? how are they configured?
