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
