- From: Arnoud <galactus@stack.urc.tue.nl>
- Date: Wed, 22 May 1996 20:20:28 +0200
- To: www-html@w3.org
-----BEGIN PGP SIGNED MESSAGE----- In article <2.2.16.19960521165203.415f6362@pop.interaccess.com>, "Harold A. Driscoll" <harold@driscoll.chi.il.us> wrote: > <BASE href="http://foo.com/images"> > ... > <IMG SRC="bar.gif"> > > The image is deferenced to > > http://foo.com/images/bar.gif Well, I suppose this has to be /images/, but why do you need a filename after it? "http://foo.com/images/" is a correct URI, isn't it? It just happens to point to a directory rather than a file. I don't see the problem here. Shouldn't the browser simply use the value from the BASE HREF as the starting point to resolve relative URLs, like it would with normal URLs? So wouldn't using "http://foo.com/images/" as base href result in /images/bar.gif in the example above? Galactus - -- To find out more about PGP, send mail with HELP PGP in the SUBJECT line to me. E-mail: galactus@stack.urc.tue.nl - Please PGP encrypt your mail if you can. Finger galactus@turtle.stack.urc.tue.nl for public key (key ID 0x416A1A35). Anonymity and privacy site: <http://www.stack.urc.tue.nl/~galactus/remailers/> -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: cp850 iQCVAgUBMaNlHTyeOyxBaho1AQExJQP/ZBXo6pGU+pBtqOarebHWGxzXzv6xuS8Q +g6LJM9Wlj6LVNrhr6P7LC2cmLyGMlGHcfqSogYtu5X/8X+s/RSuIc9GJmUv0+9W ow88rkTLrvSKpco0Q1NfEdcKKJk2FCfSe+O+AG8XKy6ShIep+RWQmwicRJyRi15Q 4IQLF67wfvg= =dmhh -----END PGP SIGNATURE-----
Received on Wednesday, 22 May 1996 15:18:36 UTC