[jira] Resolved: (WICKET-748) ServletWebRequest.getRelativePathPrefixToContextRoot generates wrong relative path

["Alastair Maw (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alastair Maw resolved WICKET-748.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.3.0-rc1)
                   1.3.0-beta3

This only happens for things with URL-encoded entities, but I guess that's quite a few things, so good catch.

Fixed in r562171.

> ServletWebRequest.getRelativePathPrefixToContextRoot generates wrong relative path
> ----------------------------------------------------------------------------------
>
>                 Key: WICKET-748
>                 URL: https://issues.apache.org/jira/browse/WICKET-748
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta2
>            Reporter: Chuck Deal
>            Assignee: Alastair Maw
>             Fix For: 1.3.0-beta3
>
>         Attachments: quickstart-relativeurl.zip
>
>
> Actually, this is against 1.3.0-SNAPSHOT revision: 554607
> I have been trying to find a very annoying, seeminly sporadic, glitch where my images that are relative to the context wouldn't "find" the image file.  Looking at the source, they would have 11 sets of ".." versus the 5 sets that the other resources would have.   Here is how I was trying to display the image:
> <img src="images/find.png"/>
>  I was finally able to produce a scenario in a quickstart to prove the problem exists.  It seems that getPath() and getServletPath() don't work the same way, in that I mean, getPath() had the '{" encoded as "%7B" whereas getServletPath() was not encoded.
> Therefore, this test fails and the path is not properly handled!
>     if (servletPath.endsWith(path))

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.