http://knownissues.blogspot.com/2008/04/ftp-redirect-1114669.html

The above bug was posted in April and has a label "fixed" associated
with it.  However, when you try to access http://dfwdraco76.blogspot.com
in IE you get a "cannot display the webpage" error.

I moved my blog from the above URL to http://www.thelifeofbrian.info/blog
a few weeks back.  The only way I've found to get a 301 redirect was
to publish my blogger blog to a custom domain
(blog.thelifeofbrian.info) and then do a 301 redirect there
via .htaccess.

It works ok in Firefox (although it prompts before redirecting, see
this thread: http://groups.google.com/group/blogger-help-howdoi/browse_thread/thre...).

Can somebody give shed some light on the IE issue?  It's confusing to
have a 3 month old bug labeled "fixed" that apparently is not fixed...

Thanks

Is this the wrong place to be asking this question?  If so, could
somebody please point me in the right direction?

On Jul 1, 8:49 pm, DFWDraco76 wrote:

On Jul 1, 6:49 pm, DFWDraco76 wrote:

Reproducing the problem will be a challenge, if you have a workaround
in place.  Right now, your readers who use IE are OK, and your readers
who use FF are slightly inconvenienced.  Is that better than the
original way, when the problem could be observed?
http://blogging.nitecruzr.net/2006/03/asking-for-help.html

Chuck [Blog*Star 2006 - 2008]
Real Blogger Status: http://blogging.nitecruzr.net/

I'm confused...

My IE users get a page cannot be displayed (or similar) message.
That's not "ok"...  I can live with FF and Opera users having to ok
the redirect, I'm concerned that none of the IE users that try to
access the old blog are being redirected.

On Jul 3, 9:30 am, nitecruzr wrote:

DFWDraco76,
I had this exact issue today.

Published to custom domain, and in Firefox, they have to click to
redirect, which is annoying, but OK. But in Safari and Internet
Exporer - they get a "cannot display the webpage"....totally Not OK.

I tried using the method you described, making a subdomain, putting
a .htaccess in that new subdomain that directs all traffic to the new
blog domain, and then changing the publishing settings to that new
subdomain. (I too have a blog that uses a folder, and geez louise why
doesn't blogger let us redirect traffic to a folder already?)

So far, the message is still coming up...so maybe it takes some time
to reset?

When you did this work around, was their any delay?
Jill

42 minutes later....still not working.
And inside Blogger, if you click on "View Blog" it is correctly
showing the subdirectory. Yet when I view the page in IE or Safari,
it's not found. In FF I get the "you're about to be redirected"
message. And the redirect URL displayed is exactly correct.

Here's the proof:
The new blog: http://www.coultertm.com/blog/
The old blog: http://www.copyrightorwrong.blogspot.com/
The workaround sub domain: http://www.blog.coultertm.com/

So I would love to get this to work like DFWDraco76 did...
J

I finally gave up on this...didn't want to leave his blog "broken" for
the long weekend.

Here's what I did:

Deactivated the redirection inside Blogger admin, let it publish on
Blogspot.
Went into the Blogger template and added:

<meta http-equiv="refresh" content="0;url=http://www.coultertm.com/
blog" />

Saved the template.

So it's a really icky solution and it sure would be nice if the
Blogger built in redirect worked with all browsers...but until I find
a solution, I will be using this.

Sigh.
J

Hey everybody...   Just to be clear -- I do not have a working
solution in place.  I get the "you're about to be redirected" in
Firefox, and IE users simply get the page cannot be displayed.

So I'm still looking / waiting for a solution too.

My question (aside from how to fix it) is about the "known issue" post
at http://knownissues.blogspot.com/2008/04/ftp-redirect-1114669.html.
It's got a label of "fixed" -- so is it supposed to be?  Clearly it is
not....

On Jul 3, 4:48 pm, Aldebaran-Jill wrote:

I posted another fellow (www.blogbloke.com) for help, and he told me
to follow his instructions on his blog article, but when I tested out
the blog he claimed was working:

http://instabloke.blogspot.com/

I get the exact same error message in IE that we're getting...

Is there another place that we should be escalating this redirect
issue?

Jill

Hi Jill. It's the other fellow here :-)

Strange, but it was working the other day when I contacted you. It
seems to me the problem is either an intermittent one or it is a
security patch recently implemented to prevent redirects to malicious
sites. If that's the case then it's a stupid brute force fix that
unfortunately ruins it for everyone. Either way you gotta love
Microsoft.

As you know the redirect still works with FF and Opera. I will keep an
eye on this and do keep me posted of further developments.

Cheers!

On Jul 6, 11:03 am, Aldebaran-Jill wrote:

For crying out loud. Now I know what the problem is. Jeesh, I must be
sleeping at the wheel today.

Jill, you are trying to redirect the old blogspot address. That won't
work because I have changed it to the custom domain url in the
publishing settings.

Like I said in my comment on my blog you need to first follow my
directions for setting up your custom domain:

http://www.blogbloke.com/custom-domain-blogger-dns-seo-godaddy-blogge...

And then implement the htaccess redirect:

http://www.blogbloke.com/migrating-redirecting-blogger-wordpress-htac...

I hope this helps.

Cheers1

On Jul 6, 11:03 am, Aldebaran-Jill wrote:

Just so you know that it works, click on my old address and you will
see the redirect in action:

http://instabloke.com

On Jul 6, 3:21 pm, blogbloke wrote:

Yes, that's exactly what I'm trying to do, and what the control panel
of Blogger seems to indicate is possible. I've done Blogger to
WordPress migrations before...and I was able to redirect everything
(the old blogspot address and every single article was properly mapped
to the new WordPress article). I realize that you've posted a tutorial
on your blog, but the only issue I am having is that I want a person
who goes to the old blog's home page to be redirected to the new
blog's home page. I know how to redirect archives and individual
posts. It's the home page redirect that I'm looking for a solution to.

As I said, I use another method (described here:
http://aldebaranwebdesign.com/blog/converting-blogger-to-wordpress/)
and it's worked perfectly on Blogger to WordPress migrations before.

So you're saying that it's not possible to redirect
http://www.copyrightorwrong.blogspot.com/ to http://www.coultertm.com?

Just to be super duper clear, we're not trying to redirect from one
domain that we own to another domain we own (as in the example:
instabloke.com to blogbloke.com).

We are trying to redirect a blogger domain that google owns to a
domain that we own.
(ex: copyrightorwrong.blogspot.com to coultertm.com)

I'm afraid that I don't understand why having http://instabloke.blogspot.com/
lead folks to a dead end if they're using Internet Explorer is not an
issue?

Jill

Still searching for a clue...found this excerpt:
"The custom domain option on blogger is only a redirect for the
blogspot address to your domain name, the content is still hosted on
blogger."
from this article: http://www.dailyseoblog.com/2007/07/moving-from-blogger-to-wordpress-...

Is it possible the custom domain option isn't supposed to do what we
think it's supposed to do? That is assumes your content is still
hosted on blogger?

Now I'm beginning to think that the best we can do is simply map over
the posts/categories that are indexed by Google (which does work) and
leave the home page redirect behind in the dust.

J

I found another good article that's relevant. You can see my comment
at the end:
http://www.sciencetext.com/blogger-custom-domain.html#comment-73271

Here's what he says:
"Yes, I’d noticed that Blogger changed the format for their redirects.
However, if you use the URL redirect server response check at SEO
tools, enter the original blogger URL and hit return/enter you will
see that it gives a 301 (moved permanently) redirect message to the
new location,which is the only thing that matters in terms of rank
being passed on to the new site."

So I went to:
http://www.seologic.com/webmaster-tools/url-redirect.php

And put in the blog I had migrated a while ago (maybe 6 months ago):
http://www.vibrancenutrition.blogspot.com

And indeed it does look like it's completely redirected correctly. But
if you put the URL in Firefox, you get the same message (do you wish
to be redirected) and it doesn't work at all in Internet Explorer. Now
when I did this migration, I am 100% sure there was no "do you wish"
message in Firefox, so I'm positive this part is new. But it appears
to be passing page rank.

So the issue of lost readership remains. For folks who use IE and who
access the blog via it's homepage, they won't be able to find your new
blog. Firefox folks are fine. And if you were lucky enough to use
Feedburner for subscriptions, those readers would also be fine. Now,
how many people read blogs by checking their home pages...I don't
know.

wow, I nod off for a couple days and look at all the action here!  lol

I see what you're saying...  But it still boils down to - why does it
work in FF & Opera, but not IE and Safari?

On Jul 6, 7:03 pm, Aldebaran-Jill wrote:

I have absolutely no idea...but it seems like it's Google's task to
make their redirect work with major browsers. The question is, how to
let them know about it and get them to fix it.

But after chatting with a few other migration bloggers, and also
looking at the results of a migration I did a few months ago that's
been properly redirected and reindexed, I've decided the best course
of action is to use the blogger redirect as is, because it's properly
redirecting the search engines, even if it's not properly redirecting
the humans.

My thought is that the humans will tend to come into the blog via it's
newly indexed articles, versus the old blogspot home page...at least
over time this will be true. So that's the route I've decided to take.
Looking at my own website stats, the number of folks who read my blog
that come into the home page is a few orders of magnitude less that
the number of folks who come directly into articles they found on
search engines.

But if you find out where to submit this issue to Google, I'll happily
help push it, because it's so obviously broken.