Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Do not try to set HTTP response code on already closed connection #47971

Merged
merged 1 commit into from
Sep 14, 2024

Conversation

come-nc
Copy link
Contributor

@come-nc come-nc commented Sep 14, 2024

Summary

This avoids a PHP warning in the logs about trying to set the response
code while the output already started. It’s useless to try to print an
error page anyway in this situation because the connection was closed
already.

Checklist

This avoids a PHP warning in the logs about trying to set the response
 code while the output already started. It’s useless to try to print an
 error page anyway in this situation because the connection was closed
 already.

Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
@come-nc come-nc added the 3. to review Waiting for reviews label Sep 14, 2024
@come-nc come-nc added this to the Nextcloud 31 milestone Sep 14, 2024
@come-nc come-nc self-assigned this Sep 14, 2024
@come-nc
Copy link
Contributor Author

come-nc commented Sep 14, 2024

/backport to stable30

@come-nc
Copy link
Contributor Author

come-nc commented Sep 14, 2024

/backport to stable29

@come-nc
Copy link
Contributor Author

come-nc commented Sep 14, 2024

/backport to stable28

@come-nc come-nc requested review from joshtrichards, a team, icewind1991, artonge, Fenn-CS and Altahrim and removed request for a team September 14, 2024 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: cannot set response code - headers already sent (PHP 8.3)
5 participants