TYPO3 Forger
  • Dashboard
  • Get involved
  • Reviews
    Overview Ready for review Work in progress Needs action Needs review Needs verification Needs rebase Negative votes Reviewed and verified Ready to merge
  • Issues
    Stale issues Possible duplicates By category By month
  • Sprints
    Overview Initiatives TYPO3 Core Review board
  • Tools
    Backports ReST helper
  • Help
  • Search
  • Login
Esc

Words find the open ones, a number the issue and the change with it.

  1. Issues
  2. #105163
Issue Task Closed

#105163Do not log Exceptions due to invalid client headers

Christoph Lehmann 09/29/24, 21:23 updated 12/02/25, 14:32

Open in Forge Comment in Forge

Description

Exceptions should not get logged, when a client sends broken headers.

- 1436717269 in \TYPO3\CMS\Core\Http\Message::validateHeaderValues()
- 1436717270 in \TYPO3\CMS\Core\Http\Message::validateHeaderName()

Reviews 3

  • 13.4 87176[TASK] Do not log exceptions due to invalid client HTTP headers Resolves this issue Merged Benni Mack CR +2 V +2 → main, 12.4 Easy +2 −0 11/22/24, 08:05
  • 12.4 87177[TASK] Do not log exceptions due to invalid client HTTP headers Resolves this issue Merged Benni Mack CR +2 V +2 → main, 13.4 Easy +2 −0 11/22/24, 07:23
  • main 86379[TASK] Do not log exceptions due to invalid client HTTP headers Resolves this issue Merged Christoph Lehmann CR +2 V +2 → 13.4, 12.4 Easy +2 −0 11/22/24, 07:11

Related issues 2

  • Bug #103129Modified "Host" header with invalid port leads to exception when creating the ServerRequestFactory->fromGlobals Related to Closed v12 Johannes Schlier 02/15/24, 11:56
  • Bug #105194Lots of log entries for invalid http requests Related to Closed Backend API v12 Markus Klein 10/04/24, 10:11
Author
Christoph Lehmann
Priority
Should have
TYPO3 version
13
© 2026 TYPO3 GmbH.
  • API
  • Privacy Policy
  • Legal Notice
  • Feedback