Ken: > /images will always reference the root of the website. > > If the developer is using a directory off the root of the website (and > marking that as an application root), then perhaps on his/her folder > structure, the /images folder isn't located off the root of the application. > But that's a problem for the developer to solve if they aren't using an > environment that mimicks production. The problem could perhaps be solved using a virtual directory in IIS. This is like a path translation - you can set up a virtual directory called /images/ and point it to /folder1/folder2/folder3/images. Then in code you can refer to /images/image.jpg and IIS will look for that file in the folder referenced above. OP: > We're working with an outside agency who is developing in .Net. We are > implementing part of their > code on WebLogic (JSPs) due to a story too long to tell. For their images > (and other paths as > well) they are using: > > src="..images/image.gif" > > Which works fine in their environment. However, when WebLogic needs to grab > an image, the ../ is > not relative. We have to call /images/ instead. So, I asked them to change > all the references > since the images dir resides in the root anyway. > > Their developer comes back and tells me it doesn't work for him. Since when > is /images/ not mean > the root in IIS or .Net?