JSON response shortcuts require an exact content-type key
A response declared as application/json; charset=utf-8 did not expose the generated .json() convenience method.
This page traces one detailed external-report case through the available source and release evidence. The public-record census includes additional discovery channels and separately identified recurrences.
- Report
- Issue #1370
- Reporter
- IhorR-DevBrother
- Reported
- August 14, 2025
- Reported version
- Not specified
- Matched window
- Included
- First affected release entered matched window
- No
- Origin classification
- Pre-existing before 2025
- Classification confidence
- High
- Chronology confidence
- Medium
- Accepted correction
- PR #1372
- First fixed release
- 1.4.2
- Report to release
- 6.55 elapsed daysReport: 2025-08-14T10:03:08Z; corrected publication: 2025-08-20T23:14:45.823Z.
Finding
The exact-match type predates 2025. PR #1372 is counted with its linked issue, not as a second external report.
Evidence trail
Origin
Confirmed affected by: 3d03bb56, committed August 13, 2022; confirmed affected release 0.8.0. The early response-builder shortcut type matched media types exactly rather than recognizing parameters such as charset.
Source history and behavioral evidence
The old conditional type requires exact key membership. The external contributor's accepted fix switches to a contains match; a later release reverted it and a separate 2026 repair restored the behavior.
Release chronology
The exact-match behavior is confirmed by 0.8.0. The initial fix shipped in 1.4.2 six days after the report.