You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Bryant Luk (JIRA)" <ji...@apache.org> on 2010/04/17 22:58:24 UTC
[jira] Created: (WINK-270) Honor Accept-Charset when returning text
based content
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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WINK-270) Honor Accept-Charset when returning
text based content
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858363#action_12858363 ]
Hudson commented on WINK-270:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #315 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/315/])
Change mediatype with a charset for text providers
This takes into account the Accept-Charset
whenever possible.
See [WINK-270]
> 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.
[jira] Resolved: (WINK-270) Honor Accept-Charset when returning
text based content
Posted by "Bryant Luk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryant Luk resolved WINK-270.
-----------------------------
Resolution: Fixed
> 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.
[jira] Closed: (WINK-270) Honor Accept-Charset when returning text
based content
Posted by "Mike Rheinheimer (JIRA)" <ji...@apache.org>.
[ 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.