@greg it is not about how servers respond, it is about how links resolved.
On Dec 14, 10:12 pm, Greg Oliver <[email protected]> wrote: > On Mon, Dec 14, 2009 at 2:05 PM, Kaan Meralan <[email protected]> wrote: > > @Mohamed, thanks for your precious google advice! > > > @PhistucK, here is an example: > > > goto:http://www.netsiparis.com/detay/11211299110/TARGUS-TCG650-NOTEBOOK-CA... > > this is a turkish e-commerce site selling different products (like > > notebook case as in here). > > > open source and search for "resimler/uyeyeni_gif.gif" (a gif for new > > members). if you click on this gif (i assume that you are in chrome or > > using ff) you will see that this relative url resolves to "http:// > >www.netsiparis.com/resimler/uyeyeni_gif.gif", although as far as i > > know it should be resolved to "http://www.netsiparis.com/detay/ > > 11211299110/resimler/uyeyeni_gif.gif". > > > this case is true nearly for all the "href"s in this page (you can > > check it for "default.asp?bolum=32" (a new category page which is > > resolved to "http://www.netsiparis.com/default.asp?bolum=32"; )) > > This could be as simple as the server configured for this... That is > how sites do redirects without modifying code... > > > > > am i confused or missing something? > > > thanks for your help... > > > On Dec 14, 8:12 am, PhistucK <[email protected]> wrote: > >> Do you mean it shows the URL you were talking about, or goes to the URL you > >> are talking about? > >> Because there might be some URL redirection the actual website is setting. > > >> You first example is weird, I have never seen it happening. > > >> ☆PhistucK > > >> On Fri, Dec 11, 2009 at 15:39, 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 -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
