i think i'll add my $.02 here... what craig says on this matter is perfectly reasonable [i previously felt this was an issue, but not a big enough one for me to raise a flag about]. something that i would like to see though is a hook into this mechanism so that if a developer desires or requires, they could easily install their own "filter" which does more or special encoding not handled by the ResponseUtil.filter() method. since all the struts tags use this centralized method before spitting out HTML, what better place to locate such functionality [transparently]? of course, such a mechanism should also be available for use outside of the struts tags in case one is inclined to not use them... On Tuesday, April 24, 2001, at 09:52 AM, Peter Alfors wrote: > Oops... I wasn't thinking... :) > Yep, I agree it shouldn't be an encoding mechanism. > > Pete > > "Craig R. McClanahan" wrote: > >> On Fri, 20 Apr 2001, Peter Alfors wrote: >> >>> Hello all, >>> >>> Is there any plan to update the ResponseUtil.filter() method to >>> handle more (or all) of the HTML special characters? >>> It looks like right now only 4 are being handled. >>> >>> Thanks, >>> Pete >>> >> >> What other characters are you concerned about? The purpose of >> filtering >> was to avoid problems where user data had HTML markup in it, but it >> wasn't >> designed to be a general purpose encoding mechanism. >> >> Craig
begin:vcard n:; x-mozilla-html:FALSE org:<BR><IMG SRC="http://www.irista.com/logo/irista.gif"><BR><BR><FONT Color=#000080><FONT SIZE=2><B>Bringing Vision to Your Supply Chain adr:;;;;;; version:2.1 end:vcard
> _______________________________________________________________________ Elod Horvath ('e') / ITFAIS Records (http://www.itfais.com/)