fix: ReferralMiddleware causing blank pages with rid query parameter#757
Merged
BenjaminMichaelis merged 7 commits intomainfrom Jul 14, 2025
Merged
fix: ReferralMiddleware causing blank pages with rid query parameter#757BenjaminMichaelis merged 7 commits intomainfrom
BenjaminMichaelis merged 7 commits intomainfrom
Conversation
Co-authored-by: BenjaminMichaelis <22186029+BenjaminMichaelis@users.noreply.github.com>
Co-authored-by: BenjaminMichaelis <22186029+BenjaminMichaelis@users.noreply.github.com>
Co-authored-by: BenjaminMichaelis <22186029+BenjaminMichaelis@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Non-content pages are returned blank with referrid query parameter
Fix ReferralMiddleware causing blank pages with rid query parameter
Jul 14, 2025
Keboo
approved these changes
Jul 14, 2025
…n, and restore error handling Co-authored-by: Keboo <952248+Keboo@users.noreply.github.com>
Keboo
approved these changes
Jul 14, 2025
BenjaminMichaelis
added a commit
that referenced
this pull request
Apr 25, 2026
…757) ## 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 a `rid` parameter was present. The middleware was missing the critical `await _Next(context);` call after referral processing, causing the request to terminate early. ## Before (Broken): ```csharp public async Task InvokeAsync(HttpContext context, IReferralService referralService, UserManager<EssentialCSharpWebUser> userManager) { string? referralId = query["rid"]; if (string.IsNullOrWhiteSpace(referralId)) { await _Next(context); // ✓ Continues pipeline when NO rid return; } // Process referral tracking referralService.TrackReferralAsync(referralId, claimsUser); // ❌ MISSING: await _Next(context); // Pipeline stops here when rid exists! } ``` ## After (Fixed): ```csharp public async Task InvokeAsync(HttpContext context, IReferralService referralService, UserManager<EssentialCSharpWebUser> userManager) { string? referralId = query["rid"]; if (string.IsNullOrWhiteSpace(referralId)) { await _Next(context); return; } try { // Process referral tracking referralService.TrackReferralAsync(referralId, claimsUser); } catch (Exception ex) { _logger.LogError(ex, "Failed to track referral ID {ReferralId}", referralId); } // ✅ FIXED: Always continue the pipeline await _Next(context); } ``` ## Changes Made 1. **Critical Fix**: Added missing `await _Next(context);` call after referral processing 2. **Error Resilience**: Added try-catch around referral tracking to prevent exceptions from breaking page rendering 3. **Logging Enhancement**: Added structured error logging for debugging referral tracking issues 4. **Test Coverage**: Added comprehensive tests to verify the fix works for all scenarios ## Verification ✅ `/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 - Pages with valid rid parameters return content - Pages with empty/whitespace rid parameters work correctly - Pages with non-rid parameters continue to work - Error scenarios are logged but don't break page rendering Fixes #756. <!-- START COPILOT CODING AGENT TIPS --> --- 💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click [here](https://survey.alchemer.com/s3/8343779/Copilot-Coding-agent) to start the survey. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: BenjaminMichaelis <22186029+BenjaminMichaelis@users.noreply.github.com> Co-authored-by: Benjamin Michaelis <git@relay.benjamin.michaelis.net> Co-authored-by: Keboo <952248+Keboo@users.noreply.github.com>
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.
Problem
Pages with
ridquery 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
ReferralMiddlewarewas processing referral tracking but failing to continue the request pipeline when aridparameter 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=abc123now renders content correctly✅
/about?rid=user-refnow 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.