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 "René Cordier (Jira)" <se...@james.apache.org> on 2021/06/16 04:18:00 UTC
[jira] [Closed] (JAMES-3600) All JMAP calls should position
Content-Length (to play well with compression)
[ https://issues.apache.org/jira/browse/JAMES-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
René Cordier closed JAMES-3600.
-------------------------------
Resolution: Fixed
> All JMAP calls should position Content-Length (to play well with compression)
> -----------------------------------------------------------------------------
>
> Key: JAMES-3600
> URL: https://issues.apache.org/jira/browse/JAMES-3600
> Project: James Server
> Issue Type: Bug
> Components: JMAP
> Affects Versions: 3.6.0
> Reporter: Benoit Tellier
> Assignee: Antoine Duprat
> Priority: Major
> Fix For: 3.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://stackoverflow.com/questions/33269448/why-is-the-gzip-minimum-length-directive-not-being-respected
> TLDR without this header NGinx ingress GZIPs everything, which might be detrimental to performance, as small payloads compression might be expensive.
> We should thus position content length for all responses being sent by JMAP server, both draft and RFC-8621.
--
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