https://issues.apache.org/jira/browse/TAPESTRY-2765
Andreas Andreou wrote:
I tried this example (and some non-ajax permutations) and i indeed see
different behavior with cookies enabled vs. disabled.
If that's not expected, then a new issue should be raised in jira.
On Fri, May 28, 2010 at 09:51, Paul Stanton <p...@mapshed.com.au> wrote:
well, its worth discussing - the question being should tapestry work with
cookies disabled.
i did notice that the jsessionid param was being appended to the form's
action however submitting said form had unexpected results.
its no longer holding me up, but i have worked on apps where cookies are not
an option (cross domain security etc) so i can imagine cases where it would
be a serious issue for someone.
the test case is there.
p.
Thiago H. de Paula Figueiredo wrote:
On Fri, 28 May 2010 00:31:18 -0300, Paul Stanton <p...@mapshed.com.au>
wrote:
Surely this is a bug in t5 ...
I disagree. HTTP is purely stateless. Session keeping is the container's
(server) responsibility, not Tapestry's. With cookies disabled, the only way
to find out what is the session is appending the ;jsessionid=xxx string to
the URLs. This is done by HttpServletResponde.encodeURL(String url), which
is indirectly invoked for every single link generated by Tapestry.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
