The request for the CSS is a renderCssReference call: response.renderCSSReference("css/styles.css");
So it should be relative to what ever protocol is being used? On 11/02/2010, at 10:58 AM, jason lea wrote: > The background image url is relative to the css file. Is the request for > the css file https? > > On Thu, Feb 11, 2010 at 12:35 PM, Steve Swinsburg <steve.swinsb...@gmail.com >> wrote: > >> Hi all, >> >> I have a Wicket application that is running over HTTPS but is rendering >> some images (like background images from css) over HTTP only. This causes >> the 'This page contains unsecure items' type warning and inspecting the Page >> Info from Firefox shows they are indeed being served over HTTP only. >> >> Luckily I can switch this particular site to be just HTTP and as soon as I >> do that, the issues go away (obviously since its all just HTTP now). However >> I cannot just run the entire app over HTTPS only, as this application is >> deployed in many different contexts by many different institutions and they >> may be running it over HTTP only. >> >> So can I force Wicket to render everything via HTTPS if its running over >> HTTPS and just normal HTTP if its running as such? >> >> Note that I have things like: >> >> .someClass { >> background-image: url(/library/image/silk/icon.png); >> } >> >> so I can't just prefix all URL links since most of them come from the CSS. >> >> thanks, >> Steve > > > > > -- > Jason Lea
smime.p7s
Description: S/MIME cryptographic signature