Can you show an example of the above, like a test case stating what you are experiencing? I can't see how that could happen.
If you visit "www.aaa.com/bbb/ccc", assuming ccc is a directory, and index.[whatever] inside it has "<a href="ttt/qqq">qqq</a>" that should bring up "www.aaa.com/bbb/ccc/ttt/qqq". If ccc is a file (that your webserver interprets), then it should be " www.aaa.com/bbb/ttt/qqq" http://www.google.ca/search?q=Relative+and+absolute+URLs -Mohamed Mansour On Fri, Dec 11, 2009 at 8:39 AM, Kaan Meralan <[email protected]> wrote: > hi everybody, > > for a long time i am curious about one thing that how browsers > correctly resolve wrongly given relative hrefs. > > here is my example: > > suppose we are at url "www.aaa.com/bbb/ccc" and what we see somewhere > in the source html is something like that : > > <a href="ddd/eee">eee</a> > > and in our browser (whatever it is) we see the actual link as > "www.aaa.com/ddd/eee". > > however in a different domain when we are at url "www.xxx.com/yyy/zzz" > and have an element > > <a href="ttt/qqq">qqq</a> > > this time our browser resolves this link as "www.xxx.com/yyy/ttt/qqq" > > > > surprising part here is that both of them are correctly resolved but > browser behaved differently! > > > > by the way same example applies when relative urls starts with "/"... > > do you have any idea how this is possible? do you know in which part > of the source code this operation is handled? > > best regards... > > -- > Chromium Discussion mailing list: [email protected] > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-discuss > -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
