You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Peter Ertl (JIRA)" <ji...@apache.org> on 2011/06/25 16:37:47 UTC
[jira] [Commented] (WICKET-3834) WicketTester does not follow
absolute redirects
[ https://issues.apache.org/jira/browse/WICKET-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054908#comment-13054908 ]
Peter Ertl commented on WICKET-3834:
------------------------------------
additionally, when the first call of tester.startPage() redirects to a secure version of the page, e.g. https://localhost/secure, the subsequent requests (e.g. form submit) should go to the same base url (https://localhost). in general wicket tester should assign the protocol://host:port of the last request to the next wicket tester request (unless the last request was of type ajax).
> WicketTester does not follow absolute redirects
> -----------------------------------------------
>
> Key: WICKET-3834
> URL: https://issues.apache.org/jira/browse/WICKET-3834
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC5.1
> Reporter: Peter Ertl
> Assignee: Peter Ertl
> Fix For: 1.5-RC6
>
>
> Wicket tester does not follow absolute redirects:
> This is a problem when using HttpsMapper. For example when requesting a page over http:// with an forced redirect to https:// for secure access will make wicket tester return 'null' for the last renderer page instead of the rendered page instance. In general all kinds of absolute redirects to another page will not be tracked by wicket tester. So this potentially a problem for all kinds of tests that rely on absolute redirects.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira