Summary: Amaya mishandling HREF values that contain ampersand

Hello,

Thank you for your reports. This is really a problem inside Amaya, and
in contradiction to the HTML 4.0 spec.

Here's our proposal:

In the forthcoming version, we'll escape the & and other entities
(e.g., ") into their characters before making a local or
remote document access.

If we find %26, we won't interpret it and send it as such to the server.
If we're making a local file access, we'll then first convert the
%26 into '&' then do search the file (i.e., doing the server's work
when there's no such server). Same strategy for other %xx chars.

This should solve the problem. 

-Jose

Received on Thursday, 8 July 1999 11:07:32 UTC