Closed Bug 845580 Opened 12 years ago Closed 11 years ago

Redirect www.mozilla.org/en-US/home/ to better location

Categories

(www.mozilla.org :: General, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: cmore, Assigned: pmac)

References

(Blocks 1 open bug)

Details

(Whiteboard: u=user c=content p=)

I just came across a page on www.mozilla.org that I had no idea exists and has no analytics on it.

http://www.mozilla.org/en-US/home/

It appears to only exist for en-US.

It appears in bug 540908, google.com/firefox was copied to firefox.com/home and when mozilla.com and mozilla.org was combined, this /home directory was created. When we finally completed the migration from google.com/firefox, we adjusted DNS to redirect users to start.mozilla.org. Thus, www.mozilla.org/home/ has no purpose and I believe it was an artifact of the mozilla.com and mozilla.org website combination project.

Code is here:

http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/en-US/home/index.html?view=log

Top redirect options:

1) Redirect to /firefox/

2) Redirect to start.mozilla.org

It is possible that these users may not be able to update and start.mozilla.org would provide appropriate messages to those users who can to upgrade their browser. I vote for option 1 unless we want to pull log files to find out who the users are.
I also vote for option 1.
Priority: -- → P3
Whiteboard: u=user c=content p=
(In reply to jbertsch from comment #1)
> I also vote for option 1.

What if these users cannot upgrade because they are running an OS that cannot run the latest version of Firefox? Though, putting the redirect in there would eliminate this page from search and we have no idea how people are getting to this page. Log files are the only answer to this.
How much effort to pull the log files?
Open bug 845614 to see if we can get some data.
Those results are surprising. Most are Fx 18/19 on some version of Windows.
(In reply to Paul McLanahan [:pmac] from comment #5)
> Those results are surprising. Most are Fx 18/19 on some version of Windows.

Yeah, I wonder if it is an old profile value for their homepage that just has transferred between upgrades?
Search for "mozilla home" or "firefox home" it may be in your list on Google near the top. I really have no idea how people are finding this URL, but they are. I made a comment in the metrics bug to find out how many are Power PC Macs since they can't upgrade.
Let's just do option 1. Redirect /en-US/home/ to /en-US/firefox/.
(In reply to Chris More [:cmore] from comment #8)
> Let's just do option 1. Redirect /en-US/home/ to /en-US/firefox/.

You got it. Just en-US or all locales? I'm guessing all.
Assignee: nobody → pmac
(In reply to Paul McLanahan [:pmac] from comment #9)
> (In reply to Chris More [:cmore] from comment #8)
> > Let's just do option 1. Redirect /en-US/home/ to /en-US/firefox/.
> 
> You got it. Just en-US or all locales? I'm guessing all.

Yes, retornam is checking into some legacy on the original idea of /home/. He remembers some reason why /home/ was created and not redirected to start.mozilla.org or /firefox/ previously. From looking at the logs, the original idea for /home/ may not be relevant anymore. If we are unsure, redirecting to start.mozilla.org would be more safe.

Let's see what Raymond digs up.
The firefox home product page was created for our IOS app Firefox Home. The product no longer exists so it is safe to redirect this to the /firefox/ page
+1 to redirect to /firefox/. Better than a 404.
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/ae923faa5e31b2dcb38a9f63cf7abdc34508861c
Bug 845580 Redirect Firefox home

https://github.com/mozilla/bedrock/commit/cbac170122c05edab768f593fe5628a2c2c2f98c
Merge pull request #958 from retornam/bug-845580-redirect-firefox-home

Bug 845580 Redirect Firefox home
fixed on dev

curl -I "https://www-dev.allizom.org/en-US/home/"
HTTP/1.1 301 Moved Permanently
Server: Apache
X-Backend-Server: bedrock1.dev.webapp.phx1.mozilla.com
Vary: Accept-Encoding
Content-Type: text/html; charset=iso-8859-1
Date: Thu, 20 Jun 2013 19:20:07 GMT
Location: https://www-dev.allizom.org/firefox/
Transfer-Encoding: chunked
Connection: Keep-Alive
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
fixed on prod   http://www.mozilla.org/home --> https://www.mozilla.org/firefox/
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.