[
https://issues.apache.org/jira/browse/HTTPCORE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649335#comment-13649335
]
Daniel Yokomizo commented on HTTPCORE-300:
------------------------------------------
Gary, parameters may be multivalued. At least nothing on RFC 2616 forbids it.
> ContentType does not support parameters
> ---------------------------------------
>
> Key: HTTPCORE-300
> URL: https://issues.apache.org/jira/browse/HTTPCORE-300
> Project: HttpComponents HttpCore
> Issue Type: Improvement
> Components: HttpCore
> Affects Versions: 4.2
> Reporter: Daniel Yokomizo
> Priority: Minor
> Fix For: 4.3-beta2
>
>
> ContentType is the class to be used in httpcore-4.2 whenever a mime type is
> expected (e.g. StringEntity, FileEntity), but it does not support parameters
> so it's not possible to use it in places where a parameters is part of the
> mime type.
> For example in an application I work on we use parameter to specify the
> applicable JSON schema, as recommended in the JSON Schema draft
> (http://tools.ietf.org/html/draft-zyp-json-schema-03)
> Content-Type:
> application/my-media-type+json;profile=http://json.com/my-hyper-schema
> It should be possible to specify parameters to a ContentType and get them
> when parsing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
