I've noticed that this issue is still present in 1.4.5. There is also a jira
issue which wasn't assigned yet:
http://issues.apache.org/jira/browse/WICKET-2312 and it has a patch attached
also.
Is there any chance for this bug being fixed in 1.4.6?
Thanks!
Alex Objelean
Alexandru Objelean wrote:
>
> I have a use-case, when I want to render absolute url for some images
> using
> a shared resource.
> The absolute url looks like this:
> http://localhost:8080/resources/org.apache.wicket.Application/com.mysite.web.util.resource.ProductImageResource?id=47331bd95fa69f7f001-main.jpg
>
> Everything works fine, except when the panel containing these images is
> updated via ajax. In this case, the absolute url looks like
> this:
> resources/org.apache.wicket.Application/com.mysite.web.util.resource.ProductImageResource?id=47449058d8e54c7f001-main.jpg
>
> The problem is dependent on UrlCodingStrategy used. For instance, there is
> no problem if QueryStringUrlCodingStrategy is used. On the other hand,
> when BookmarkablePageRequestTargetUrlCodingStrategy
> or MixedParamUrlCodingStrategy is used, then the problem can be
> reproduced.
>
> It is very probable, that when using this kind of url coding strategies,
> the
> algorithm of computing absolute url's should be slightly different.
>
> Alex Objelean
>
>
--
View this message in context:
http://old.nabble.com/-BUG--RequestUtils.toAbsolutePath%28%29-for-ajax-requests-tp26872309p27202742.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
