Comments on: Shit happens, your redirects hit the fan! http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/ If you've read my articles somewhere on the Internet, expect something different here. Thu, 24 Jul 2008 16:06:17 +0000 http://wordpress.org/?v=2.2.3 By: Anon Coward http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-1091 Anon Coward Thu, 31 Jan 2008 07:03:30 +0000 http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-1091 ok looks like the blog engine is removing the link to the JS file. It is just a regular js link but with the src set to AmIAuthenticated.aspx on the authentication server

ok looks like the blog engine is removing the link to the JS file. It is just a regular js link but with the src set to AmIAuthenticated.aspx on the authentication server

]]> By: Anon Coward http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-1088 Anon Coward Wed, 30 Jan 2008 14:32:14 +0000 http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-1088 Is what you output using Response.Write Missed out that bit on my original post... (after 'To do this output this to the bottom of your page using Response.Write or whatever:' Is what you output using Response.Write

Missed out that bit on my original post…

(after ‘To do this output this to the bottom of your page using Response.Write or whatever:’

]]> By: Anon Coward http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-1087 Anon Coward Wed, 30 Jan 2008 14:27:59 +0000 http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-1087 Kristin - Here is (half) a .Net solution that I use (obviously very easy to write in php, ruby - anything). Do not automatically redirect anyone who hasn't already got a session on your Single Sign-On Server. But how do I do this you ask! Ok, here we go... In your content page if an authenticated session for the user does not exist then you need to check the Single Sign-on server to see if there is one there, right? To do this output this to the bottom of your page using Response.Write or whatever: "" As you can see this links into a code page on your Single Sign-on Server, not a javascript file (you could set up isapi filters or whatever to make the .js extension map to the .apsx handler also). What does AmIAuthenticated.aspx return? This: ---begin code If (Session("username") Is Nothing) Then returnScript = "" Else If (Request.UrlReferrer Is Nothing) Then returnScript = "window.location = '" ConfigurationSettings.AppSettings ("SessionServerUrl").ToString() "';" Else returnScript = "window.location = '" ConfigurationSettings.AppSettings("SessionServerUrl").ToString() "?redirectUrl=" Server.UrlEncode(Request.UrlReferrer.AbsoluteUri) "';" End If End If ---end code So if there was a session it takes the user (using JavaScript window.location) to the Single Sign-On server to pick up there ticket! So you only redirect people if js / cookies are working, and if they have already logged into you Single Sign-On Server, not search engine crawlers! Ok, I think that should get you started... P.s. If you can't get this going it is because of my bad explanation, the method works, I am using it... Kristin - Here is (half) a .Net solution that I use (obviously very easy to write in php, ruby - anything).

Do not automatically redirect anyone who hasn’t already got a session on your Single Sign-On Server.

But how do I do this you ask!

Ok, here we go…

In your content page if an authenticated session for the user does not exist then you need to check the Single Sign-on server to see if there is one there, right?

To do this output this to the bottom of your page using Response.Write or whatever:

“”

As you can see this links into a code page on your Single Sign-on Server, not a javascript file (you could set up isapi filters or whatever to make the .js extension map to the .apsx handler also).

What does AmIAuthenticated.aspx return?

This:

—begin code

If (Session(”username”) Is Nothing) Then
returnScript = “”
Else
If (Request.UrlReferrer Is Nothing) Then
returnScript = “window.location = ‘” ConfigurationSettings.AppSettings (”SessionServerUrl”).ToString() “‘;”

Else
returnScript = “window.location = ‘” ConfigurationSettings.AppSettings(”SessionServerUrl”).ToString() “?redirectUrl=” Server.UrlEncode(Request.UrlReferrer.AbsoluteUri) “‘;”
End If
End If

—end code

So if there was a session it takes the user (using JavaScript window.location) to the Single Sign-On server to pick up there ticket!

So you only redirect people if js / cookies are working, and if they have already logged into you Single Sign-On Server, not search engine crawlers!

Ok, I think that should get you started…

P.s. If you can’t get this going it is because of my bad explanation, the method works, I am using it…

]]> By: Sebastian http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-873 Sebastian Thu, 20 Dec 2007 20:56:15 +0000 http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-873 Not sure why a ticket benefits a crawler, actually I guess that's worthless, so why not checking for legit search engine crawlers and delivering those the contents without any redirects? Not sure why a ticket benefits a crawler, actually I guess that’s worthless, so why not checking for legit search engine crawlers and delivering those the contents without any redirects?

]]> By: kristin http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-871 kristin Thu, 20 Dec 2007 20:31:00 +0000 http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-871 Right now, I am redirecting 3 times for every page visit. 1. Redirect to the Single Sign-On server to get a ticket. 2. Redirect back to the page (service url) from the Single Sign-On server 3. Self-redirect without the ticket parameter This ofcourse is pissing off Google's web crawler. Any solution to avoid this? Right now, I am redirecting 3 times for every page visit.
1. Redirect to the Single Sign-On server to get a ticket.
2. Redirect back to the page (service url) from the Single Sign-On server
3. Self-redirect without the ticket parameter

This ofcourse is pissing off Google’s web crawler. Any solution to avoid this?

]]> By: The anatomy of a server sided redirect: 301, 302 and 307 illuminated SEO wise http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-518 The anatomy of a server sided redirect: 301, 302 and 307 illuminated SEO wise Tue, 09 Oct 2007 14:58:32 +0000 http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-518 [...] whatever) when it runs into a redirect condition. Some redirects are done by the server itself (see handling incomplete URIs), and there are several places where you can set (conditional) redirect directives: Apache’s [...] […] whatever) when it runs into a redirect condition. Some redirects are done by the server itself (see handling incomplete URIs), and there are several places where you can set (conditional) redirect directives: Apache’s […]

]]> By: Lorna http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-503 Lorna Sat, 06 Oct 2007 11:45:31 +0000 http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-503 This is a great post for Googlebot dum-dums such as myself. I'm checking my server logs immediately. This is a great post for Googlebot dum-dums such as myself. I’m checking my server logs immediately.

]]> By: Paul Pedersen http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-484 Paul Pedersen Thu, 27 Sep 2007 17:17:43 +0000 http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-484 Great post. I've seen a great deal of this over the years. Great post. I’ve seen a great deal of this over the years.

]]> By: TheMadHat http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-483 TheMadHat Thu, 27 Sep 2007 16:28:41 +0000 http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-483 We moved a site about 6 months ago with 90k pages. We were doing chaing redirects (around 3) and everything blew up. Sitemaps wouldn't validate and pages were not being reindexed very quickly. We had to modify the backend to do away with any obvious redirects. A lot more difficult in IIS as Carsten mentioned. It quickly bounced back (quickly being a couple weeks) after we fixed it. We moved a site about 6 months ago with 90k pages. We were doing chaing redirects (around 3) and everything blew up. Sitemaps wouldn’t validate and pages were not being reindexed very quickly. We had to modify the backend to do away with any obvious redirects. A lot more difficult in IIS as Carsten mentioned. It quickly bounced back (quickly being a couple weeks) after we fixed it.

]]> By: Melanie Phung http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-480 Melanie Phung Thu, 27 Sep 2007 13:43:42 +0000 http://sebastians-pamphlets.com/how-to-avoid-troubles-caused-by-chained-redirects/#comment-480 Heh heh. I'm sending this one over to all my developers. Heh heh. I’m sending this one over to all my developers.

]]>