fix: ReferralMiddleware causing blank pages with rid query parameter #757
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.
Problem
Pages with
rid
query parameter (e.g.,/guidelines?rid=abc123
) were returning blank content with HTTP 200 status, while the same pages without the parameter worked correctly.Root Cause
The
ReferralMiddleware
was processing referral tracking but failing to continue the request pipeline when arid
parameter was present. The middleware was missing the criticalawait _Next(context);
call after referral processing, causing the request to terminate early.Before (Broken):
After (Fixed):
Changes Made
await _Next(context);
call after referral processingVerification
✅
/guidelines?rid=abc123
now renders content correctly✅
/about?rid=user-ref
now renders content correctly✅ Referral tracking functionality preserved
✅ Error scenarios handled gracefully
✅ Backward compatibility maintained
Test Cases Added
Fixes #756.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.