I think you are right; I'm using Firefox 1.0.4 and haven't tested this in other browsers yet (Eriks workaround solved the problem before I got to that).
My issue was that the browser ended up sending a GET request to the servlet container with embedded & sequences. I thought it was a problem that Tapestry output these in the first place (still not sure I understand why it is being done) but you may be right that it is a browser issue. On Thursday 26 May 2005 16:05, Pierre-Yves Nicolas wrote: > > Yes I did; doesn't appear to work on Tomcat 5.5.9 > > If there is a problem, it's with the browser, not the servlet > container. I think the way Tapestry outputs URLs is the good one, and > Tomcat should not do anything about it. But the browser has to > correctly decode the URL inside the HTML. > If the HTML document contains > <a href="/page?foo=1&bar=2"> > and if you click on this link, the browser should go to /page?foo=1&bar=2 > Is it not the case ? > > I'm not sure I understand your issue... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
