Bug #77427
closedWrong spelling of Content-Type header may lead to duplicate header
100%
Description
While debugging a BE login problem, I noticed that the response object in the ajax/rsa/publickey handler contains two Content-Type headers:
protected 'headers' => array (size=3) 'Content-type' => array (size=1) 0 => string 'application/json; charset=utf-8' (length=31) 'X-JSON' => array (size=1) 0 => string 'true' (length=4) 'Content-Type' => array (size=1) 0 => string 'text/html; charset=utf-8' (length=24)
It looks like my browser is automatically ignoring the older header, so the last one takes precedence and the other one is removed. Nevertheless, I think that it could lead to problems in some circumstances.
(My original problem has been solved in the meantime. I can tell for sure that it is not related to the issue I'm describing here. However, it should still be fixed...)
My suggestion is to fix the spelling of "Content-Type" in all places to prevent eventual problems.
See also: https://www.ietf.org/rfc/rfc2616.txt
Updated by Gerrit Code Review almost 8 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49410
Updated by Gerrit Code Review almost 8 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49410
Updated by Michael Stucki almost 8 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset bef279d33b11b3dd0d969d7a63c9ae9b03daa7d0.