[
https://issues.apache.org/jira/browse/WICKET-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893022#comment-17893022
]
Pedro Henrique Oliveira dos Santos commented on WICKET-7024:
------------------------------------------------------------
Hi, I was taking a look in the ticket referenced in code related to this
behavior [1], and the URL attributes encoded to inform the resource style seams
to be designed to resource URLs only. I added a new test [2] in the
PackageResourceReference to only decode such URLs, avoiding to misread the
callback ones as with locale, style... encoded information, and it seams to fix
this issue. Working on a test case.
1 - https://issues.apache.org/jira/browse/WICKET-5909
2 -
https://github.com/pedrosans/wicket/commit/dca94258201aae475884416c7869475f45e37755
> Wrong static resource urls when their generation is triggered by <wicket:link>
> ------------------------------------------------------------------------------
>
> Key: WICKET-7024
> URL: https://issues.apache.org/jira/browse/WICKET-7024
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 9.12.0
> Reporter: Martin Tzvetanov Grigorov
> Priority: Major
> Attachments: wicket-link-leak.tgz
>
>
> If an application uses <wicket:link> to generate a url for a static resource,
> e.g.
> {code:java}
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:wicket="http://wicket.apache.org/">
> <head>
> <wicket:head>
> <wicket:link>
> <link rel="stylesheet" type="text/css" href="css/test2.css" />
> </wicket:link>
> </wicket:head>
> </head>
> ... {code}
> then during the page render time it will use
> {code:java}
> CharSequence url = getRequestCycle().urlFor(handler); {code}
> and
> [https://github.com/apache/wicket/blob/bc70f127ff74f154890a35be906b55db5bdc8683/wicket-core/src/main/java/org/apache/wicket/request/resource/PackageResourceReference.java#L117-L128]
> will use the current page's url and try to parse locale/style/variation from
> it and embed it in the static resource url.
> The problem is that it uses the pageId/renderCount/behaviorId and component
> path instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)