Of course, you’re right, however, the error log was reporting an entry against “http://www.mydomain.co.uk/products” NOT the JS file that was to be included.

I could see why apache would report that it couldn’t find the JS, but it could. In the temptate used at the time, the base href tag actually sorted the relative issue anyway.

With “/js/monkey.js”, this is treated as a path relative to the application root.

With “js/monkey.js”, this is treated as a path relative to the current address.

Here are some examples:

On http://www.mydomain.co.uk/, both includes would be pointing at /js/monkey.js

On http://www.mydomain.co.uk/products/, the first script would still be pointing at /js/monkey.js but the second (without the leading slash) would be pointing at /products/js/monkey.js