This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 50%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
I have the below code that redirects the url (used -MaximumRedirection 0) to a normal. My concern is to check specifically if the url redirect is to login page instead of redirect in general. Is that possible?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
Wouldn't a "Redirect" response code fall in the 3xx range?
Yes Rich.
Just a concern from my end as I see it, this is really non-futureproof, as redirects is a normal one - may be something in Frontend configured and in Sitecore, by doing this we will get errors once we have such logic in place somewhere.
A redirect message will have the new URL in the message body. It may be in a "<meta>" tag, or it may appear as "location: URL".
The "meta" tag would look something like this:
head
meta http-equiv="Refresh" content="0; URL=https://NewURL.com/"
/head
NOTE: I couldn't post the example with the "<" and ">" in there. This Q&A "protection" is exasperating!
Could you help me how can I implement logic if the url redirect is to login page?
Why don't you just hire Rich to write this application for you? Sign an NDA and give him access to the web sites and a list of project requirements.
It seems to me that it would be much simpler than this piecemeal back and forth multiple question process that we've been engaged with.
Its really hard to guess as to what a web site is going to return on any given call. So asking any of us to write code to process calls to a site that we can't test against is just going to be based on assumptions. We have no way to know how the actual site authenticates users or handles redirects or is going to respond to any given request.
I think your expectations are out of line with the reality of asking for help and at the same time maintaining anonymity and not divulging the URL and providing access so that we can test.
Sorry, I had to vent.
I'm pretty sure that web search engines are available to you. Do you use them?
how-to-test-for-a-http-url-redirect-in-powershell
getting-redirected-uris-in-powershell
I think it's important for you to refer to the article below on "Redirect URI (Response URL) Restrictions and Limitations" which will help you to better understand what is possible and what is not in the scenario you are facing:
https://learn.microsoft.com/en-us/azure/active-directory/develop/reply-url
----
--If the answer is helpful, please vote positively and accept the answer--