Repository navigation
Clarify HTTP 4xx/5xx failures from feed reads - #146
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix FeedIo
eader
eaderrorexception on HTTP 403 response
Clarify HTTP 4xx/5xx failures from feed reads
Oct 4, 2026
Grotax
marked this pull request as ready for review
October 17, 2026 05:19
Grotax
approved these changes
Oct 17, 2026
Co-authored-by: Grotax <5429298+Grotax@users.noreply.github.com>
Grotax
force-pushed
the
copilot/fix-feedio-reader-readerror
branch
from
October 17, 2026 05:27
7e0c8f2 to
67d1d60
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feed reads could fail with a generic
internal server erroreven when the remote endpoint was actively rejecting the request, which made debugging 403/500 responses difficult and forced callers to do pre-flight checks.Summary
What changed
ServerErrorExceptionnow reports values likeServer responded with: 403 Forbiddeninstead of the hard-codedinternal server error.Example