You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Wouter de Vaal (JIRA)" <ji...@apache.org> on 2011/03/15 12:15:29 UTC
[jira] Created: (WICKET-3535) wicket does not handle /. requests
correctly - should show homepage
wicket does not handle /. requests correctly - should show homepage
-------------------------------------------------------------------
Key: WICKET-3535
URL: https://issues.apache.org/jira/browse/WICKET-3535
Project: Wicket
Issue Type: Bug
Affects Versions: 1.4.16
Reporter: Wouter de Vaal
- Deploy a wicket webapp as root.
- Create a page with a link that will call setResponsePage(HomePage.class);
- Use internet explorer 8
when clicking the response will be something like:
HTTP/1.1 302 Moved Temporarily
Server: Apache-Coyote/1.1
Location: http://localhost:8080/.
Internet explorer will show an empty 404 page.
This problem does not occur in firefox or chrome, because they clean up the request url to / (without the dot).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3535) wicket does not handle /. requests
correctly - should show homepage
Posted by "Pedro Santos (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009344#comment-13009344 ]
Pedro Santos commented on WICKET-3535:
--------------------------------------
Can't reproduce here, I tested the following code in 1.4.16 and IE 8:
add(new Link("link1") {
@Override
public void onClick() {
setResponsePage(HomePage.class);
}
});
add(new BookmarkablePageLink("link2", HomePage.class));
> wicket does not handle /. requests correctly - should show homepage
> -------------------------------------------------------------------
>
> Key: WICKET-3535
> URL: https://issues.apache.org/jira/browse/WICKET-3535
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.4.16
> Reporter: Wouter de Vaal
>
> - Deploy a wicket webapp as root.
> - Create a page with a link that will call setResponsePage(HomePage.class);
> - Use internet explorer 8
> when clicking the response will be something like:
> HTTP/1.1 302 Moved Temporarily
> Server: Apache-Coyote/1.1
> Location: http://localhost:8080/.
> Internet explorer will show an empty 404 page.
> This problem does not occur in firefox or chrome, because they clean up the request url to / (without the dot).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-3535) wicket does not handle /. requests
correctly - should show homepage
Posted by "Pedro Santos (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pedro Santos resolved WICKET-3535.
----------------------------------
Resolution: Cannot Reproduce
Assignee: Pedro Santos
send a quickstart showing the problem please and reopen the ticket
> wicket does not handle /. requests correctly - should show homepage
> -------------------------------------------------------------------
>
> Key: WICKET-3535
> URL: https://issues.apache.org/jira/browse/WICKET-3535
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.4.16
> Reporter: Wouter de Vaal
> Assignee: Pedro Santos
>
> - Deploy a wicket webapp as root.
> - Create a page with a link that will call setResponsePage(HomePage.class);
> - Use internet explorer 8
> when clicking the response will be something like:
> HTTP/1.1 302 Moved Temporarily
> Server: Apache-Coyote/1.1
> Location: http://localhost:8080/.
> Internet explorer will show an empty 404 page.
> This problem does not occur in firefox or chrome, because they clean up the request url to / (without the dot).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira