What steps will reproduce the problem?
1. Write a test with a FormAuthentication
RestAssured.authentication = form("myuser", "secret", new
FormAuthConfig("/authenticate", "username", "password"));
2. Test with a login method that sets a session cookie and redirects to another
resource with a 303.
// Play Framework 2.0 controller
session().put("username", username);
return redirect(routes.Application.index());
3. In the next request the session cookie is lost and the user is not
authenticated anymore.
If I change the redirect to a 302 found response, the behavior is correct and
the cookie is not lost.
For my tests I used 1.7 as well as 1.8.0.
Original issue reported on code.google.com by tilmanpo...@googlemail.com on 5 Jun 2013 at 3:30
Original issue reported on code.google.com by
tilmanpo...@googlemail.com
on 5 Jun 2013 at 3:30