You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2021/10/15 03:46:00 UTC
[jira] [Commented] (JAMES-3662) Accept CORS headers without the
JMAP API restriction on "Accept" headers
[ https://issues.apache.org/jira/browse/JAMES-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429104#comment-17429104 ]
Benoit Tellier commented on JAMES-3662:
---------------------------------------
> The default jmap API being used when not specified in the Accept header is jmap-draft.
There is a configuration option to control this by the way, so this statement is deployment dependant...
> We need to allow bypassing the Accept headers for the CORS options in James for the JMAP API.
+1
> Accept CORS headers without the JMAP API restriction on "Accept" headers
> ------------------------------------------------------------------------
>
> Key: JAMES-3662
> URL: https://issues.apache.org/jira/browse/JAMES-3662
> Project: James Server
> Issue Type: Improvement
> Reporter: René Cordier
> Priority: Major
> Fix For: 3.7.0
>
>
> The default jmap API being used when not specified in the Accept header is jmap-draft. That seems to create issues for web browser applications that try to accept to JMAP RFC8621 API that need to do a preflight request, as you can't seem to be able to specify a custom Accept header ({{Accept: */*}})
> We need to allow bypassing the Accept headers for the CORS options in James for the JMAP API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org