[ 
https://issues.apache.org/jira/browse/WICKET-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288635#comment-13288635
 ] 

Martin Grigorov commented on WICKET-4561:
-----------------------------------------

Please open a new ticket with a quickstart.
Thanks!
                
> Wicket 1.5.6 duplicates segments in absolute URLs
> -------------------------------------------------
>
>                 Key: WICKET-4561
>                 URL: https://issues.apache.org/jira/browse/WICKET-4561
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.6
>            Reporter: Dirk Forchel
>            Assignee: Martin Grigorov
>             Fix For: 1.5.7, 6.0.0-RC1
>
>         Attachments: quickstart.zip
>
>
> Since we migrate our application to Wicket 1.5.6 some URLs from 
> BookmarkablePageLinks have duplicate segements for indicating a Shop and a 
> Language item from our persistence model. For indicating a Shop and Language 
> item we use our own ShopMapper and LanguageMapper (subclass of 
> AbstractComponentMapper). This was working until we migrate to 1.5.6.
> For instance ...
> correct URL: host/servlet/shop/en/page
> wrong URL: host/servlet/shop/en/shop/en/page
> This happens, for example, when the protocol of the linked URL is different 
> from the current protocol (http/https). So, basically, all links that point 
> to pages that are annotated with @RequireHttps are wrong.
> In our Application class we set the HttpsMapper as RootRequestMapper, e.g.:
> setRootRequestMapper(new HttpsMapper(new ShopMapper(new 
> LanguageMapper(getRootRequestMapper())), new HttpsConfig() ) );
> Using a debugger, I've tracked down the spot where wrong URL is rendered:
> org.apache.wicket.request.Url.resolveRelative()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to