Bug 7636 - <fmt:requestEncoding> Ignores Browser's request encoding
Summary: <fmt:requestEncoding> Ignores Browser's request encoding
Status: RESOLVED INVALID
Alias: None
Product: Taglibs
Classification: Unclassified
Component: Standard Taglib (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-30 19:48 UTC by David Geary
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Geary 2002-03-30 19:48:13 UTC
doEndTag() is implemented like this:

public int doEndTag() throws JspException {
	if ((value == null)
	      && (pageContext.getRequest().getCharacterEncoding() == null)) {
	    /*
	     * no charset specified in tag or defined in request Content-Type
	     * header
	     */
	    value = (String) pageContext.findAttribute(REQUEST_CHAR_SET);
	}

	if (value != null) {
	    try {
		pageContext.getRequest().setCharacterEncoding(value);
	    } catch (UnsupportedEncodingException uee) {
		throw new JspTagException(uee.getMessage());
	    }
	}

	return EVAL_PAGE;
    }

If pageContext.getRequest().getCharacterEncoding() returns a non-null value, 
that value is ignored.
Comment 1 Shawn Bayern 2002-03-30 21:02:22 UTC
David wrote:

> Sorry, this is not a bug. The implementation of doEndTag() is correct.
> 
> 
> david