A complete html parser seems a bit over the top if you can ensure the html
is validated before it goes into the database.
If the html is validated you can perform a search and replace on known
cases, however I had the same problem and encodeURL only worked on url's
that could be resolved within your own context (?!).

A javascript call for example which ends by calling document.location.href
= args[0] (which you might call through javascript:myFunction('myurl')) is
a nasty problem to get right I think. I solved my problem by including a
cookie check ;-)). Not the solution you are looking for I think, but it is
a solution.

greetz
Hans
At 15:57 15/08/2003 +0200, Ralph Einfeldt wrote:
>That is how it works. AFAIK there is nothing you can
>configure to change this.
>
>This is a thing that requires some logic to implement a
>generic solution. It would require a complete html parser
>that parses each response (Quite challanging and time
>consuming). And what should this solution do with
>javascript ? Another solution would be a taglib that
>replaces <bean:write/> with a tag that parses the output
>before it is given to the response.
>
> > -----Original Message-----
> > From: Kurt Overberg [mailto:kurt@(protected)]
> > Sent: Friday, August 15, 2003 3:45 PM
> > To: Tomcat Users List
> > Subject: Re: URLEncoding urls (hrefs) that are coming out of a
> > database...
> >
> > Well, yeah it should, but I get the impression (from testing
> > and seeing it not do it) that if the URL is coming from a
> > database and the URL (a href) is embedded in other text, that
> > it won't automagically work.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
>For additional commands, e-mail: tomcat-user-help@(protected)


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)