You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ivan Vasilev (JIRA)" <ji...@apache.org> on 2011/01/16 19:17:43 UTC
[jira] Created: (WICKET-3340) Custom error 404 page and page id-s
Custom error 404 page and page id-s
-----------------------------------
Key: WICKET-3340
URL: https://issues.apache.org/jira/browse/WICKET-3340
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.5-M3
Environment: Windows 7, Chrome 9, Firefox 3.6
Reporter: Ivan Vasilev
Attachments: quickstart.rar
>From this discussion:
http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
There is a custom error 404 page created as described here:
http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
The example can be found in the attached quickstart. Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3340) Custom error 404 page and page id-s
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-3340.
-----------------------------------
Resolution: Invalid
> Custom error 404 page and page id-s
> -----------------------------------
>
> Key: WICKET-3340
> URL: https://issues.apache.org/jira/browse/WICKET-3340
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Environment: Windows 7, Chrome 9, Firefox 3.6
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Attachments: quickstart.rar, quickstart.tgz
>
>
> From this discussion:
> http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
> There is a custom error 404 page created as described here:
> http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
> The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
> The example can be found in the attached quickstart. Thanks.
> Edit:
> The issue turned out to be pretty trivial. The browsers automatically make requests for url "/favicon.ico" (something I didn't know) and I didn't have favicon.ico in my application. After adding it the error disappeared.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3340) Custom error 404 page and page id-s
Posted by "Ivan Vasilev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Vasilev updated WICKET-3340:
---------------------------------
Attachment: quickstart.rar
> Custom error 404 page and page id-s
> -----------------------------------
>
> Key: WICKET-3340
> URL: https://issues.apache.org/jira/browse/WICKET-3340
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Environment: Windows 7, Chrome 9, Firefox 3.6
> Reporter: Ivan Vasilev
> Attachments: quickstart.rar
>
>
> From this discussion:
> http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
> There is a custom error 404 page created as described here:
> http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
> The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
> The example can be found in the attached quickstart. Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3340) Custom error 404 page and page id-s
Posted by "Ivan Vasilev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982396#action_12982396 ]
Ivan Vasilev commented on WICKET-3340:
--------------------------------------
I had it compiled for 1.5-m3, but thanks for the conversion.
Here is how I reproduce the issue:
1. It reproduces every time with Google Chrome version 9.05.597.47
2. I place a conditional breakpoint in MountedMapper on line 161 with condition
url.getSegments().get(0).equals("404")
2. from the browser I open "localhost:8080"
3. If the server is recently started the first url I see is http://localhost:8080/home?0.
4. Again, I open "localhost:8080". This time the url is http://localhost:8080/home?2.
Each time the page id is incremented with 2 the conditional breakpoint is hit, so I assume that a request for the error 404 page is made
The Chrome part is important, currently I cannot reproduce it with Firefox.
Thanks.
> Custom error 404 page and page id-s
> -----------------------------------
>
> Key: WICKET-3340
> URL: https://issues.apache.org/jira/browse/WICKET-3340
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Environment: Windows 7, Chrome 9, Firefox 3.6
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Attachments: quickstart.rar, quickstart.tgz
>
>
> From this discussion:
> http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
> There is a custom error 404 page created as described here:
> http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
> The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
> The example can be found in the attached quickstart. Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3340) Custom error 404 page and page id-s
Posted by "Ivan Vasilev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Vasilev updated WICKET-3340:
---------------------------------
Description:
>From this discussion:
http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
There is a custom error 404 page created as described here:
http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
The example can be found in the attached quickstart. Thanks.
Edit:
The issue turned out to be pretty trivial. The browsers automatically make requests for url "/favicon.ico" (something I didn't know) and I didn't have favicon.ico in my application. After adding it the error disappeared.
was:
>From this discussion:
http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
There is a custom error 404 page created as described here:
http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
The example can be found in the attached quickstart. Thanks.
> Custom error 404 page and page id-s
> -----------------------------------
>
> Key: WICKET-3340
> URL: https://issues.apache.org/jira/browse/WICKET-3340
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Environment: Windows 7, Chrome 9, Firefox 3.6
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Attachments: quickstart.rar, quickstart.tgz
>
>
> From this discussion:
> http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
> There is a custom error 404 page created as described here:
> http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
> The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
> The example can be found in the attached quickstart. Thanks.
> Edit:
> The issue turned out to be pretty trivial. The browsers automatically make requests for url "/favicon.ico" (something I didn't know) and I didn't have favicon.ico in my application. After adding it the error disappeared.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (WICKET-3340) Custom error 404 page
and page id-s
Posted by "Ivan Vasilev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982396#action_12982396 ]
Ivan Vasilev edited comment on WICKET-3340 at 1/16/11 5:14 PM:
---------------------------------------------------------------
I did the quickstart for 1.5-m3, but thanks for the conversion.
Here is how I reproduce the issue:
1. It reproduces every time with Google Chrome version 9.05.597.47
2. I place a conditional breakpoint in MountedMapper on line 161 with condition
url.getSegments().get(0).equals("404")
2. from the browser I open "localhost:8080"
3. If the server is recently started the first url I see is http://localhost:8080/home?0.
4. Again, I open "localhost:8080". This time the url is http://localhost:8080/home?2.
Each time the page id is incremented with 2 the conditional breakpoint is hit, so I assume that a request for the error 404 page is made
The Chrome part is important, currently I cannot reproduce it with Firefox.
Thanks.
was (Author: hok):
I had it compiled for 1.5-m3, but thanks for the conversion.
Here is how I reproduce the issue:
1. It reproduces every time with Google Chrome version 9.05.597.47
2. I place a conditional breakpoint in MountedMapper on line 161 with condition
url.getSegments().get(0).equals("404")
2. from the browser I open "localhost:8080"
3. If the server is recently started the first url I see is http://localhost:8080/home?0.
4. Again, I open "localhost:8080". This time the url is http://localhost:8080/home?2.
Each time the page id is incremented with 2 the conditional breakpoint is hit, so I assume that a request for the error 404 page is made
The Chrome part is important, currently I cannot reproduce it with Firefox.
Thanks.
> Custom error 404 page and page id-s
> -----------------------------------
>
> Key: WICKET-3340
> URL: https://issues.apache.org/jira/browse/WICKET-3340
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Environment: Windows 7, Chrome 9, Firefox 3.6
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Attachments: quickstart.rar, quickstart.tgz
>
>
> From this discussion:
> http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
> There is a custom error 404 page created as described here:
> http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
> The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
> The example can be found in the attached quickstart. Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WICKET-3340) Custom error 404 page and page id-s
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reassigned WICKET-3340:
---------------------------------------
Assignee: Martin Grigorov
> Custom error 404 page and page id-s
> -----------------------------------
>
> Key: WICKET-3340
> URL: https://issues.apache.org/jira/browse/WICKET-3340
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Environment: Windows 7, Chrome 9, Firefox 3.6
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Attachments: quickstart.rar
>
>
> From this discussion:
> http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
> There is a custom error 404 page created as described here:
> http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
> The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
> The example can be found in the attached quickstart. Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3340) Custom error 404 page and page id-s
Posted by "Pedro Santos (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982919#action_12982919 ]
Pedro Santos commented on WICKET-3340:
--------------------------------------
I guess Ivan solved the ticket, it is an expected behavior since Wicket chain the request to /favicon.ico, that when is not found is handled back by Wicket, that instance an PageNotFound. As all pages are born dirty, the page set the next available id.
> Custom error 404 page and page id-s
> -----------------------------------
>
> Key: WICKET-3340
> URL: https://issues.apache.org/jira/browse/WICKET-3340
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Environment: Windows 7, Chrome 9, Firefox 3.6
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Attachments: quickstart.rar, quickstart.tgz
>
>
> From this discussion:
> http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
> There is a custom error 404 page created as described here:
> http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
> The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
> The example can be found in the attached quickstart. Thanks.
> Edit:
> The issue turned out to be pretty trivial. The browsers automatically make requests for url "/favicon.ico" (something I didn't know) and I didn't have favicon.ico in my application. After adding it the error disappeared.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3340) Custom error 404 page and page id-s
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-3340:
------------------------------------
Attachment: quickstart.tgz
I cannot reproduce the problem.
Your application didn't compile against 1.5-RC1.
1) Page#onInitialize() is final now
2) AjaxRequestTarget#appendJava*S*cript
I'm attaching corrected app against 1.5-SNAPSHOT that works correctly.
Please either explain how to reproduce the problem or close the ticket.
> Custom error 404 page and page id-s
> -----------------------------------
>
> Key: WICKET-3340
> URL: https://issues.apache.org/jira/browse/WICKET-3340
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-M3
> Environment: Windows 7, Chrome 9, Firefox 3.6
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Attachments: quickstart.rar, quickstart.tgz
>
>
> From this discussion:
> http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-td3220118.html
> There is a custom error 404 page created as described here:
> http://www.mkyong.com/wicket/how-do-configure-404-error-page-in-wicket-solution/
> The homepage TestPage contains single Form (stateful) and TestPageLink contains an AjaxLInk. When opened for the first time the id of each page shown in the url is 0. When reloaded the id increments with a value more than 1 (different values in chrome and firefox). The reason for this is that when each page is requested there is a subsequent request for the error 404 page and since this error is also handled by the WicketFilter and the id of the page is incremented with more than 1.
> The example can be found in the attached quickstart. Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.