Bug #76340
closedAjax response exceeds limit of header section -> Backport #50509 to 6.2.x
0%
Description
Using some "newer" infrastructure of TYPO3 6.2 to make metaseo compatible to 7.6, we were faced with an old problem:
X-JSON header contains a JSON object which can easily exceed a limit of ~8kb for http response headers in full-blown hosting environments.
As a workaround, we had to use jsonbody instead of json (which seems to default to jsonhead in 6.2). This is solved by #50509 in 7.x but the corresponding patch never got backported to 6.2.x (although #50509 shows 6.2.0 as the target version which is wrong). https://github.com/mblaschke/TYPO3-metaseo/issues/233
Plus, I'd rather classify #50509 as a bug (together with this issue) as common hosting environments are easily broken without the patch applied (e.g. jweiland via https://github.com/mblaschke/TYPO3-metaseo/issues/225 ). Plus, was this issue hard to track down (no errors shown to customers to begin with).
This issue contains the risk that when the patch of #50509 is applied to 6.2.x, it could break consumers which expect the JSON object to be in the header ONLY instead of the body. Using the old Ext.JS version 3.4.1.1 we had no problem with that, however.