You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bug #47516 [HttpFoundation] Prevent BinaryFileResponse::prepare from adding content type if no content is sent (naitsirch)
This PR was squashed before being merged into the 4.4 branch.
Discussion
----------
[HttpFoundation] Prevent BinaryFileResponse::prepare from adding content type if no content is sent
| Q | A
| ------------- | ---
| Branch? | 4.4
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Tickets | Fix#47473
| License | MIT
| Doc PR | -
Until now, `BinaryFileResponse::prepare()` adds `Content-Type` and other content related header even if no content is sent. This happens for example if the provided file's modification date is not older than the cached version of the client and http status 304 is sent. See issue #47473
Commits
-------
e6275ea [HttpFoundation] Prevent BinaryFileResponse::prepare from adding content type if no content is sent
0 commit comments