[
https://issues.apache.org/jira/browse/CMIS-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080216#comment-16080216
]
Tom Groeneboer edited comment on CMIS-1038 at 7/10/17 11:52 AM:
----------------------------------------------------------------
I've just created CMIS-1039, which would be nice to have for the next release.
I see that the project has been targeted to .NET Standard 1.1, which is very
nice. We've created a fork of this project on our internal repository
containing the .NET Standard 1.1 change and this MimeType change. So for us, it
would be very convenient to see a release coming soon :)
was (Author: tgroeneboer):
I've just created CMIS-1039, which would be nice to have for the next release.
I see that the project has been targeted to .NET Standard 1.1, which is very
nice. We've created a fork of this project on our internal repository
containing the .NET Standard 1.1 change and this MimeType change. So for us, it
would be very nice to see a release coming soon :)
> MimeTypes are not set correctly on setContentStream
> ---------------------------------------------------
>
> Key: CMIS-1038
> URL: https://issues.apache.org/jira/browse/CMIS-1038
> Project: Chemistry
> Issue Type: Bug
> Components: portcmis
> Affects Versions: PortCMIS 0.2.0
> Reporter: Tom Groeneboer
> Assignee: Florian Müller
> Fix For: PortCMIS 0.3.0
>
>
> Setting the {{MimeType}} on the {{ContentStream}} in the {{setContentStream}}
> does not work. The client always sets the Mime-Type on the
> {{AtomPubHttpContent}} to {{BindingConstants.MediaTypeEntry}}.
> Expected behavior:
> Set the Mime Type on requests to the Mime Type that is passed into the
> content stream.
> See AtomPubBinding.cs line 2878.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
