Skip to content

Conversation

@josephperrott
Copy link
Member

Previously the response redirect would complete the http response, but then we would attempt to still provide a status response and message, which caused errors throughout our logging. The correct action is to no longer perform response actions after a redirect.

… sent on dns redirect

Previously the response redirect would complete the http response, but then we would attempt to still provide a status response and message,
which caused errors throughout our logging.  The correct action is to no longer perform response actions after a redirect.
@josephperrott josephperrott added the action: merge The PR is ready for merge by the caretaker label Apr 30, 2025
…of material.angular.io subdomains

The subdomains attr on the request object is actually in reverse order of the subdomains as they are made in the request, because of this
we simply put the subdomains back in the original order replacing only the hostname with angular.dev instead of angular.io.
@josephperrott josephperrott changed the title fix(apps): correct error where multiple repsonses are attempted to be sent on dns redirect a couple fixes for dns redirecting Apr 30, 2025
@josephperrott josephperrott requested a review from clydin April 30, 2025 16:14
@josephperrott josephperrott removed the request for review from devversion April 30, 2025 16:15
@josephperrott
Copy link
Member Author

This PR was merged into the repository by commit a4538b2.

The changes were merged into the following branches: main

josephperrott added a commit that referenced this pull request Apr 30, 2025
…of material.angular.io subdomains (#2756)

The subdomains attr on the request object is actually in reverse order of the subdomains as they are made in the request, because of this
we simply put the subdomains back in the original order replacing only the hostname with angular.dev instead of angular.io.

PR Close #2756
@josephperrott josephperrott deleted the fix-responses branch April 30, 2025 16:16
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 31, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants