[
https://issues.apache.org/jira/browse/TRINIDAD-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794536#action_12794536
]
Scott O'Bryan commented on TRINIDAD-1233:
-----------------------------------------
Possibly, but that would be up to the container. Truthfully, there is no
guarentee that 2 portlets will have the same version of Trinidad deployed.
Even if were the case, the image exists on the producer, not on the consumer.
So it would still need to be encoded.
I personally think creating a branch for every resource is a little overly
complex, but so long as we encode urls for portlets, I guess I don't really
care. Your solution would keep us spec compliant..
> URLs in generated CSS might include ;jessionid=xxxx
> ---------------------------------------------------
>
> Key: TRINIDAD-1233
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1233
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Affects Versions: 1.2.9-core
> Environment: Trinidad 1.2.10-SNAPSHOT
> tomcat 6.0.14
> tomcat 5.5
> Reporter: Harald Kuhn
> Attachments: CSSUtils.java.patch
>
>
> Depending on the Servlet-Container URLs in the generated CSS-file may include
> the Session-Id (of the session that initiated the generation).
> i.e.
> background-image:url(/aim/css/skin/airplus/img/dialogclose.gif;jsessionid=8A002E216A7B2BF42735740787DBF102.tomcat)
> This part of the URL should be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
