W3C home > Mailing lists > Public > www-amaya@w3.org > July to September 1999

Re: preventing absolute path extension with copy and paste

From: Christian Czech <cc@derago.com>
Date: Wed, 11 Aug 1999 19:54:54 +0200
Message-ID: <002101bee422$9de45340$6f64a8c0@CC2>
To: <www-amaya@w3.org>
> Amaya tries to generate relative paths as often as possible.
> If it doesn't it could be due to an existing base element in the document
> (check the head in the structure view) or the fact that you are editing
> some pages as local files and others as through the server.
> If you are in the later case, you have to choose either to edit all pages
> as local pages or to edit through the server. That needs to install the PUT
> (a script is provided, see http://www.w3.org/Amaya/User/put.html).
> All the W3C team uses Amaya to publish directly on the http://www.w3.org 
> server.

Ok. All editing is done "locally" on our server. Let's give an example.

The homepage is at d:\www

I copy a part from a page at d:\www\Presse\index.html with href=../Bullet.gif

if I paste that image to a page at d:\www\test.html it's correctly resolved to href=Bullet.gif 

but if I paste it to a page at d:\www\Files\index.html it is resolved to d:\www\Bullet.gif which is wrong and dangerous, because it only works internally.

Nothing is posted directly to www.derago.com because we currently only have a dial up connection to the web. So because our whole page is maintained with Amaya we have to check daily if there is d:\www anywhere on our page.

derago, Wiesenstr. 3-5, 79807 Lottstetten, Germany, http://www.derago.com
Received on Wednesday, 11 August 1999 14:45:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:20 UTC