[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wink-dev
Subject:    [jira] Closed: (WINK-270) Honor Accept-Charset when returning text
From:       "Mike Rheinheimer (JIRA)" <jira () apache ! org>
Date:       2010-07-23 14:29:11
Message-ID: 1975184.544871279895351103.JavaMail.jira () thor
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/WINK-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Mike Rheinheimer closed WINK-270.
---------------------------------


Issue is resolved.  Closing per Bryant's approval to do so.

> Honor Accept-Charset when returning text based content
> ------------------------------------------------------
> 
> Key: WINK-270
> URL: https://issues.apache.org/jira/browse/WINK-270
> Project: Wink
> Issue Type: Improvement
> Components: Common
> Affects Versions: 1.1
> Reporter: Bryant Luk
> Assignee: Bryant Luk
> Fix For: 1.1
> 
> 
> The Accept-Charset can be honored when returning content to a client.  So if \
> Accept-Charset: shift-jis;q=0.8, *;q=0.2 is used, then shift-jis should be used as \
> the highest priority encoding for JAXB, String, etc. content instead of defaulting \
> straight to UTF-8.  While the JAX-RS spec does not currently dictate this, we \
> should add it. if a user sets the content-type on the Response, should not change \
> that.  If a Content-Type is not specified (i.e. taking some automatic values via \
> @Produces or combination of Accept header), then add a charset.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[prev in list] [next in list] [prev in thread] [next in thread]