Nick Murtagh [mailto:[EMAIL PROTECTED] wrote: > > deelan wrote: > > > > <style type="text/css">@import url("styles/weblog.css");</style> > > > > the problem is that webware searches for such CSS files > > under the /param1/param2/ folders (of course both are > > fictional): > > > > /WK/weblog/index/param1/param2/styles/print.css > > Relative URLs are converted into absolute ones by the web browser. > So there is nothing Webware can do about this.
Yes, this is a real area of black magic in the sense that the application writer would want the relative URLs resolved in terms of the "real part" of the URL. It's true that the browser doesn't know better, but Webware could certainly help by either providing a hook for templating systems to find out the base URL so that links are presented to the browser correctly (as suggested by Stephan Diehl, although one surely can use relative URLs with care, provided that the base URL reflects that "real part" of the requested URL as opposed to a simple, standard URL), or by doing more advanced resource discovery. I looked into this recently, although I ended up putting off any investigation because I wanted to have consistent behaviour across different frameworks. Certainly, what one does need from Webware is a correct definition of the "path info" so that any solution works properly, and there was something strange about either Webware or Apache in that regard. I'll have to dig out the details... Paul ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
