Without really digging into this, it looks to me to be an issue where your
CSS file is being served and in your CSS you have a URL in the CSS that is
causing a bad URL to be sent to the server - which Wicket is picking up and
doesn't know what to do with it.

It's this: url(iepngfix.htc)

Use a tool like Firebug or DebugBar for IE to watch what HTTP requests are
made - see where your CSS is requested, and then the browser is likely
requesting a bad URL to load iepngfix.htc.  Make it so that the URL for both
doesn't hit Wicket, and you'll be fine.

--
Jeremy Thomerson
http://www.wickettraining.com



On Thu, Mar 26, 2009 at 3:53 PM, Serkan Camurcuoglu <
[email protected]> wrote:

> we had used iepngfix.htc method, but our css file was relative to our web
> application, so iepngfix.htc file was not served through wicket.. but I
> believe it should not be problematic.. does it cause any obvious error in
> the application other than the error log?
>
>
>
> novotny wrote:
>
>> Hi,
>>
>> In order to support .png files on IE we added a "fix/hack" as documented
>> here http://www.twinhelix.com/css/iepngfix/
>>
>> However in the logs we're seeing this wicket error:
>>
>> org.apache.wicket.WicketRuntimeException: Internal error parsing
>> wicket:interface = iepngfix.htc
>>       at
>>
>> org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.addInterfaceParameters(WebRequestCodingStrategy.java:596)
>>       at
>>
>> org.apache.wicket.request.target.coding.BookmarkablePageRequestTargetUrlCodingStrategy.decode(BookmarkablePageRequestTargetUrlCodingStrategy.java:104)
>>       at
>>
>> com.homeaccount.web.wicket.WebRequestCodingStrategy.targetForRequest(WebRequestCodingStrategy.java:498)
>>       at
>>
>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:184)
>>       at org.apache.wicket.RequestCycle.step(RequestCycle.java:1246)
>>
>> Has anyone else had this problem and is there a way to deal with it?
>>
>> Thanks, Jason
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to