Re: Cost of redirect and site domain switch? Good Practice/ Bad Practice / Terrible Practice

On Mon, Aug 20, 2012 at 12:19 AM, Jim Lucas <lists@cmsws.com> wrote: > On 8/17/2012 6:35 PM, Jim Giner wrote: >> >> On 8/17/2012 7:16 PM, Jim Lucas wrote: >>> >>> >>> You could simply remove all full domain+path URL links and replace >>> them with absolute path urls only. >>> >>> turn http://www.somedomain.com/path/to/my/webpage.html >>> >>> into /path/to/my/webpage.html >>> >>> This would work with either domain. >>> >> Those would be "relative paths", ..o? >> > > No. > > Quick Google search turns up this: > > > http://www.uvsc.edu/disted/decourses/dgm/2120/IN/steinja/lessons/06/06_04.html > > I have three description or types of paths that I use normally. > > I feel the first two generally get grouped together by most persons. > > Full or complete path: > <a href="d�� ��x > $�y�ȵ0�http://www.cmsws.com/index.php">Home</a> > > Absolute Path: > <a href="/index.php">Home</a> > > Relative: > <a href="index.php">Home</a> > > -- > Jim Lucas > http://cmsws.com Actually, from what I've seen most people consider your first example an absolute path and your last example relative. The middle example, which you have called absolute, seems to be oft ignored in the explanations I found in my own "quick Google search." Even the example you cited seems to ignore the variant that you call an absolute path. A page I found on About.com (http://webdesign.about.com/od/beginningtutorials/a/aa040502a.htm) does group the first two examples together as absolute paths, but the definition of a URI on Wikipedia (http://en.wikipedia.org/wiki/Uniform_resource_identifier) disagrees -- under the section titled Examples of URI references, note this example: /relative/URI/with/absolute/path/to/resource.txt The most authoritative resource I found was from the IETF (RFC 3986). Section 4.3, as I understand it, says that an absolute URI includes the scheme part (e.g. http, ftp, tel, mailto), which would imply that your middle example is NOT an absolute path. http://tools.ietf.org/html/rfc3986#section-4.3 Andrew