http://www.johanlaidlaw.dk/2008/03/02/base-tag-href/ ruby, rails, mac, php, mobile, google, *geek* Thu, 29 Sep 2011 12:25:43 +0000 hourly 1 http://wordpress.org/?v=3.3 http://www.johanlaidlaw.dk/2008/03/02/base-tag-href/comment-page-1/#comment-8 Johan Laidlaw Tue, 04 Mar 2008 10:39:21 +0000 http://www.johanlaidlaw.dk/?p=12#comment-8 You're right.. I'm (was) confused :) The reason I wrote this was because I started working on a site where the base was set to the root (www.test.somedomain.com) and I was going to work local on my mac (http://localhost/~username/domain). All the links were set with the / in front, meaning I could not place the site where I wanted it to be. Now we have removed all the starting slashes in the links and the base tag I guess will be needless. You’re right.. I’m (was) confused The reason I wrote this was because I started working on a site where the base was set to the root (www.test.somedomain.com) and I was going to work local on my mac (http://localhost/~username/domain). All the links were set with the / in front, meaning I could not place the site where I wanted it to be. Now we have removed all the starting slashes in the links and the base tag I guess will be needless.

]]> http://www.johanlaidlaw.dk/2008/03/02/base-tag-href/comment-page-1/#comment-7 Philippe Lhoste Tue, 04 Mar 2008 10:12:13 +0000 http://www.johanlaidlaw.dk/?p=12#comment-7 You seem a bit confused... The notation is the same as for Unix directory system: the / in front of a path tells to start from the root directory, which is the top-level domain. The primary interest of the base tag is to tell where is the root of the site: it allows to use a unique directory for images, one for CSS, one for JS, and so on, put just below the root, even if your page is located deep in a hierarchy. Alternatives: - Don't specify a base. Files without an initial slash are reached relative to the location of the page, which might result in ../../images/foo.gif with number of .. depending on the depth. Can be fine for page specific files, annoying for files (images, CSS, JS) common to the whole site. - Give a base with a folder, like you show. Files are relative to this folder, which can be interesting if you have several distinct parts in your site (the blog, the forum, etc.). You seem a bit confused…
The notation is the same as for Unix directory system: the / in front of a path tells to start from the root directory, which is the top-level domain.
The primary interest of the base tag is to tell where is the root of the site: it allows to use a unique directory for images, one for CSS, one for JS, and so on, put just below the root, even if your page is located deep in a hierarchy.
Alternatives:
- Don’t specify a base. Files without an initial slash are reached relative to the location of the page, which might result in ../../images/foo.gif with number of .. depending on the depth. Can be fine for page specific files, annoying for files (images, CSS, JS) common to the whole site.
- Give a base with a folder, like you show. Files are relative to this folder, which can be interesting if you have several distinct parts in your site (the blog, the forum, etc.).

]]>