Monday, May 30, 2005 02:43 PM
when making references to shared 'html' files such as .css, .js, and images, i always find it's best to refer to them using a '/' to return to server root directory then the application context root 'myapp'. for example:
this way, if you have include files that may be included in other files that are sitting in different directory levels, you are certain to refer to the path directly. fixed fully qualified URL is painful if you move from environment to environment (e.g QA to production). relative URL (the way you have it), is just that...relative to what?