[jira] Closed: (STR-2147) [taglib] Character encodings in html tags

["Paul Benedict (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/struts/browse/STR-2147?page=all ]

Paul Benedict closed STR-2147.
------------------------------

    Fix Version/s: 1.1.1
       Resolution: Not A Problem
         Assignee:     (was: Struts Developers)

The reporter clearly misunderstood the difference between character encoding and filtering. Characters outside the normal ASCII range will not be interpreted by the User Agent unless the correct encoding is set. This is not the same as filtering.

> [taglib] Character encodings in html tags
> -----------------------------------------
>
>                 Key: STR-2147
>                 URL: http://issues.apache.org/struts/browse/STR-2147
>             Project: Struts 1
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1 Final
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Ephemeris Lappis
>            Priority: Minor
>             Fix For: 1.1.1
>
>
> HTML tags sometimes seem to encode characters before they write them into the 
> page output. In these cases, characters like '<' are translated into '&lt;', 
> that is right. But in other cases, the characters are not correctly encoded, 
> and the resulting pages can't be processed by the receiving UA. Here some 
> cases :
> - It seems that strings from resources in attributes like 'altKey' 
> or 'titleKey' are never encoded and characters like '"' lead the browser to 
> fail.
> - Attribute values set in the tag body seems to be written as is and produce 
> the same problem.
> The tags documentation doesn't specify clearly when characters are encoded and 
> when they are not, and, if they are, what kind of encoding is performed : from 
> what i can see, encodings seem to take into account characters that could break 
> the tagged structure, like '<', '\'', '"' and '>', but latin characters 
> like 'é' or 'ñ' are left as is when the page charset is set to UTF-8, for 
> example. Is it right ? In other cases, other thags like in the 'bean' family, 
> seem to encode some characters when the content type is not "text/html" 
> but "plain/text" !
> Is there a more precise documentation about content and character encodings ? 
> Is this process deterministic ?
> Thanks for your help.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira