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/24 17:55:46 UTC
[jira] Created: (WICKET-3380) HttpsMapper and BookmarkablePageLink
HttpsMapper and BookmarkablePageLink
------------------------------------
Key: WICKET-3380
URL: https://issues.apache.org/jira/browse/WICKET-3380
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.5-RC1
Reporter: Ivan Vasilev
There is a wicket Application which is configured to use HttpsMapper.
There are two page: TestPage and TestPage2. TestPage uses @RequireHttps, TestPage2 doesn't. Each page contains a BookmarkablePageLink to the other one. However in this configuration (one with @RequireHttps and one without) the links on the pages are pointing to the page they are added to - the link in TestPage links to TestPage itself (and not to TestPage2) and vice versa. When both of the pages use @RequireHttps or not using it at all the links work normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WICKET-3380) HttpsMapper and BookmarkablePageLink
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reassigned WICKET-3380:
---------------------------------------
Assignee: Martin Grigorov
> HttpsMapper and BookmarkablePageLink
> ------------------------------------
>
> Key: WICKET-3380
> URL: https://issues.apache.org/jira/browse/WICKET-3380
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Attachments: quickstart.rar
>
>
> There is a wicket Application which is configured to use HttpsMapper.
> There are two page: TestPage and TestPage2. TestPage uses @RequireHttps, TestPage2 doesn't. Each page contains a BookmarkablePageLink to the other one. However in this configuration (one with @RequireHttps and one without) the links on the pages are pointing to the page they are added to - the link in TestPage links to TestPage itself (and not to TestPage2) and vice versa. When both of the pages use @RequireHttps or not using it at all the links work normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3380) HttpsMapper and BookmarkablePageLink
Posted by "Ivan Vasilev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Vasilev updated WICKET-3380:
---------------------------------
Attachment: quickstart.rar
> HttpsMapper and BookmarkablePageLink
> ------------------------------------
>
> Key: WICKET-3380
> URL: https://issues.apache.org/jira/browse/WICKET-3380
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Ivan Vasilev
> Attachments: quickstart.rar
>
>
> There is a wicket Application which is configured to use HttpsMapper.
> There are two page: TestPage and TestPage2. TestPage uses @RequireHttps, TestPage2 doesn't. Each page contains a BookmarkablePageLink to the other one. However in this configuration (one with @RequireHttps and one without) the links on the pages are pointing to the page they are added to - the link in TestPage links to TestPage itself (and not to TestPage2) and vice versa. When both of the pages use @RequireHttps or not using it at all the links work normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3380) HttpsMapper and
BookmarkablePageLink
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985925#action_12985925 ]
Martin Grigorov commented on WICKET-3380:
-----------------------------------------
The quickstart is not working.
First, I needed to specify the ports for the HttpsConfig - 8080 and 8443.
Then it failed with:
javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:117)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1650)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:925)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1089)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1116)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1100)
at org.eclipse.jetty.server.ssl.SslSocketConnector$SslConnectorEndPoint.run(SslSocketConnector.java:640)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
at java.lang.Thread.run(Thread.java:595)
Can you provide a working one ?
> HttpsMapper and BookmarkablePageLink
> ------------------------------------
>
> Key: WICKET-3380
> URL: https://issues.apache.org/jira/browse/WICKET-3380
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Attachments: quickstart.rar
>
>
> There is a wicket Application which is configured to use HttpsMapper.
> There are two page: TestPage and TestPage2. TestPage uses @RequireHttps, TestPage2 doesn't. Each page contains a BookmarkablePageLink to the other one. However in this configuration (one with @RequireHttps and one without) the links on the pages are pointing to the page they are added to - the link in TestPage links to TestPage itself (and not to TestPage2) and vice versa. When both of the pages use @RequireHttps or not using it at all the links work normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3380) HttpsMapper and BookmarkablePageLink
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-3380.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC2
Fixed with r1062958.
Thanks!
> HttpsMapper and BookmarkablePageLink
> ------------------------------------
>
> Key: WICKET-3380
> URL: https://issues.apache.org/jira/browse/WICKET-3380
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Fix For: 1.5-RC2
>
> Attachments: quickstart.rar
>
>
> There is a wicket Application which is configured to use HttpsMapper.
> There are two page: TestPage and TestPage2. TestPage uses @RequireHttps, TestPage2 doesn't. Each page contains a BookmarkablePageLink to the other one. However in this configuration (one with @RequireHttps and one without) the links on the pages are pointing to the page they are added to - the link in TestPage links to TestPage itself (and not to TestPage2) and vice versa. When both of the pages use @RequireHttps or not using it at all the links work normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Commented] (WICKET-3380) HttpsMapper and
BookmarkablePageLink
Posted by "Sven Meier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072521#comment-13072521 ]
Sven Meier commented on WICKET-3380:
------------------------------------
Reverted to fix Wicket-3917, quickstart works fine here anyway.
> HttpsMapper and BookmarkablePageLink
> ------------------------------------
>
> Key: WICKET-3380
> URL: https://issues.apache.org/jira/browse/WICKET-3380
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC1
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Fix For: 1.5-RC2
>
> Attachments: quickstart.rar
>
>
> There is a wicket Application which is configured to use HttpsMapper.
> There are two page: TestPage and TestPage2. TestPage uses @RequireHttps, TestPage2 doesn't. Each page contains a BookmarkablePageLink to the other one. However in this configuration (one with @RequireHttps and one without) the links on the pages are pointing to the page they are added to - the link in TestPage links to TestPage itself (and not to TestPage2) and vice versa. When both of the pages use @RequireHttps or not using it at all the links work normally.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WICKET-3380) HttpsMapper and
BookmarkablePageLink
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985932#action_12985932 ]
Martin Grigorov commented on WICKET-3380:
-----------------------------------------
I made it working.
I'll debug it now.
> HttpsMapper and BookmarkablePageLink
> ------------------------------------
>
> Key: WICKET-3380
> URL: https://issues.apache.org/jira/browse/WICKET-3380
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Ivan Vasilev
> Assignee: Martin Grigorov
> Attachments: quickstart.rar
>
>
> There is a wicket Application which is configured to use HttpsMapper.
> There are two page: TestPage and TestPage2. TestPage uses @RequireHttps, TestPage2 doesn't. Each page contains a BookmarkablePageLink to the other one. However in this configuration (one with @RequireHttps and one without) the links on the pages are pointing to the page they are added to - the link in TestPage links to TestPage itself (and not to TestPage2) and vice versa. When both of the pages use @RequireHttps or not using it at all the links work normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.