[TRINIDAD-2130] Skinning: support separate style sheets for secure + non-secure pages

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.0.1-core
• Component/s: Skinning
• Assignee: Andy Schwartz
• Reporter: Andy Schwartz
• Created: 17/Aug/11 20:35
• Updated: 21/Feb/12 20:41
• Resolved: 23/Sep/11 13:11

Description

I have an ExternalContext wrapper that modifies urls that are passed to ExternalContext.encodeResourceURL(). This includes urls for images referenced by Trinidad skin definitions.

One possible modification involves converting relative URLs to absolute URLs (eg. prepending a CDN prefix), including the protocol/host/port.

A problem with this is that we share a single generated style sheet across http and https pages. This means that if I generate absolute uris with the "http:" protocol, these uris will be written into a generated .css file that would be shared by secure/https pages, in which case the browser may warn about mixed secure/non-secure content.

I would like to avoid this issue by enhancing Trinidad skinning to support generation of separate style sheets for secure and non-secure pages. That way, my ExternalContext wrapper could produce absolute uris with the appropriate protocol for the current request and avoid mixing secure/non-secure content.