You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Thomas Götz (JIRA)" <ji...@apache.org> on 2012/05/16 13:53:02 UTC

[jira] [Commented] (WICKET-4561) Wicket 1.5.6 duplicates segements in absolute URLs

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

Thomas Götz commented on WICKET-4561:
-------------------------------------

I debugged this to the following point:

Url.resolveRelative(final Url relative):

relative.segments.size=2 (de_DE/secure.html)

after line 1012: getSegments().addAll(relative.getSegments());

--> relative.segments.size=3 (de_DE/de_DE/secure.html)



                
> Wicket 1.5.6 duplicates segements 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
>         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