What I meant to say was that the ContextImage and CSS looks fine, however the actual URLs it renders are all HTTP, not HTTPS when they should be. The first resource link is clearly broken.
cheers, Steve On 11/02/2010, at 12:13 PM, Steve Swinsburg wrote: > Hi Jeremy, > > For resources its rendered as > http://myserver/webapp/context/resources/org.apache.wicket.ajax.AbstractDefaultBehaviour/indicator.gif > > For a ContextImage its: > <img src="images/no_image.gif"/> > > For the CSS include its: > <link rel="stylesheet" type="text/css" href="css/styles.css" /> > > It all looks fine except the styles.css that has the classes are sending the > images over HTTP, and they declare like: > > > >>> .someClass { >>> >>> background-image: url(/library/image/silk/icon.png); >>> >>> } > > > > > cheers, > Steve > > > > > > On 11/02/2010, at 11:53 AM, Jeremy Thomerson wrote: > >> What URL does Wicket generate in your HTML? >> >> -- >> Jeremy Thomerson >> http://www.wickettraining.com >> >> >> >> On Wed, Feb 10, 2010 at 6:46 PM, Steve Swinsburg >> <steve.swinsb...@gmail.com>wrote: >> >>> Note that this also happens for resources that Wicket serves, eg: >>> >>> resources/org.apache.wicket.ajax.AbstractDefaultBehaviour/indicator.gif >>> >>> and ContextImages. >>> >>> Can I detect HTTPS and force Wicket to serve content over HTTPS? >>> >>> thanks, >>> Steve >>> >>> >>> On 11/02/2010, at 11:14 AM, Steve Swinsburg wrote: >>> >>> 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
