> is the /resources/.... path local to the user or to the server? The url is a file:/// type url that points to a file on the local filesystem.
> in the first case it could be the browser preventing a site from > accessing your local file system, which might be allowed if it > sees it is a local html file. Ah... maybe you're right! That could explain why it works with a local file (which could allow the browser to assume that it is granted permissions to use files on the local filesystem) but not from a file served remotely. Hmmmm... interesting idea. When I get back into the office tomorrow (I'm in Asia time), I'll try serving up a static file remotely to test this theory. If this is a permission problem, I wonder if there is a way around it... > Maybe i missed an earlier post about this but why do you use file://.... ? Because my designer wants to be able to play around with the CSS without having to mount an entire development version of Wicket. It is especially tricky for us, since we are using it with OSGi, and the development setup is not trivial for a non-programmer. So, he can just do something like: http://www.blah.com/top/index.html?css=file:///path/to/css And wicket will use this. This system works perfectly well for a http:// url. I'm trying to simply things for the designer by making it work with file:/// urls. Thank you all for your ideas! Cheers, Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
