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 confusing error when webfinger request returns empty document #16986

Merged
merged 1 commit into from
Nov 14, 2021

Conversation

ClearlyClaire
Copy link
Contributor

For some reason, some misconfigured servers return an empty document when queried over webfinger.
Since an empty document does not lead to a parse error, the error is not caught properly and triggers uncaught exceptions later on.

This PR fixes that by immediately erroring out with Webfinger::Error on getting an empty response.

For some reason, some misconfigured servers return an empty document when
queried over webfinger. Since an empty document does not lead to a parse
error, the error is not caught properly and triggers uncaught exceptions
later on.

This PR fixes that by immediately erroring out with `Webfinger::Error` on
getting an empty response.
@ClearlyClaire
Copy link
Contributor Author

Also, merging this PR would make #15605 even more useful.

@Gargron Gargron merged commit 3517867 into mastodon:main Nov 14, 2021
Gargron pushed a commit that referenced this pull request Nov 26, 2021
…6986)

For some reason, some misconfigured servers return an empty document when
queried over webfinger. Since an empty document does not lead to a parse
error, the error is not caught properly and triggers uncaught exceptions
later on.

This PR fixes that by immediately erroring out with `Webfinger::Error` on
getting an empty response.
kadoshita pushed a commit to kadoshita/mastodon that referenced this pull request Nov 28, 2021
…stodon#16986)

For some reason, some misconfigured servers return an empty document when
queried over webfinger. Since an empty document does not lead to a parse
error, the error is not caught properly and triggers uncaught exceptions
later on.

This PR fixes that by immediately erroring out with `Webfinger::Error` on
getting an empty response.
ClearlyClaire added a commit to ClearlyClaire/mastodon that referenced this pull request Jan 28, 2022
…stodon#16986)

For some reason, some misconfigured servers return an empty document when
queried over webfinger. Since an empty document does not lead to a parse
error, the error is not caught properly and triggers uncaught exceptions
later on.

This PR fixes that by immediately erroring out with `Webfinger::Error` on
getting an empty response.
noellabo pushed a commit to fedibird/mastodon that referenced this pull request Mar 25, 2024
…stodon#16986)

For some reason, some misconfigured servers return an empty document when
queried over webfinger. Since an empty document does not lead to a parse
error, the error is not caught properly and triggers uncaught exceptions
later on.

This PR fixes that by immediately erroring out with `Webfinger::Error` on
getting an empty response.
noellabo pushed a commit to fedibird/mastodon that referenced this pull request Sep 9, 2024
…stodon#16986)

For some reason, some misconfigured servers return an empty document when
queried over webfinger. Since an empty document does not lead to a parse
error, the error is not caught properly and triggers uncaught exceptions
later on.

This PR fixes that by immediately erroring out with `Webfinger::Error` on
getting an empty response.
noellabo pushed a commit to fedibird/mastodon that referenced this pull request Sep 19, 2024
…stodon#16986)

For some reason, some misconfigured servers return an empty document when
queried over webfinger. Since an empty document does not lead to a parse
error, the error is not caught properly and triggers uncaught exceptions
later on.

This PR fixes that by immediately erroring out with `Webfinger::Error` on
getting an empty response.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants