Remove mozilla.org/careers and forward it to careers.mozilla.org

VERIFIED FIXED

Status

VERIFIED FIXED
7 years ago
6 years ago

People

(Reporter: wenzel, Assigned: jlong)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [2/3 8:00 PST] r=101079 b=trunk)

(Reporter)

Description

7 years ago
With the new Mozilla careers page going live towards the end of the quarter (bug 712331), we'll need to retire/remove the current careers page and just forward that subdirectory to careers.mozilla.org, where the new site will live.

This is a simple change we'll need to push basically at the same time the other site goes live, but that shouldn't be a problem.

Comment 1

7 years ago
(In reply to Fred Wenzel [:wenzel] from comment #0)
> With the new Mozilla careers page going live towards the end of the quarter
> (bug 712331), we'll need to retire/remove the current careers page and just
> forward that subdirectory to careers.mozilla.org, where the new site will
> live.
> 
> This is a simple change we'll need to push basically at the same time the
> other site goes live, but that shouldn't be a problem.

Fred,

Is there a reason we need to move to a sub-domain? adding Laura F., I think we're trying to stay consistent for seo and not using subdomains for items like this. Let us know, thanks!

Comment 2

7 years ago
Also, why is bug 712331 private? My team needs to consult on the content before anything goes live.
(Reporter)

Comment 3

7 years ago
(In reply to mcbmoz from comment #1)
> Is there a reason we need to move to a sub-domain?

Yes, technical necessity. IT can't currently deploy a database-backed mozilla.org for us, and the careers page needs a database, so we pulled that component out into a separate app for now to unblock the process.

Once bedrock is up and running and IT can provide the infrastructure to back this part of the site out of various data centers, I see no problem with moving it back into bedrock (in fact, I'd prefer that), but for now, we can't.

As far as SEO goes, Google and friends recognize redirects, so we should be fine with the current setup and be able to pull careers back into a subdirectory later to no ill effect.

(In reply to John Slater from comment #2)
> Also, why is bug 712331 private?

It's an IT push bug, those are private by default as they contain server names, settings, passwords etc. Christie CCed you on it.

Comment 4

7 years ago
+1 on moving forward with a subdomain now since the current careers site is pretty lousy and bleeds pagerank really bad given that it is sending 100% of the rank over to jobvite.com. With a domain subdomain the rank comes back into the moz.org space and I agree that a directory in the future will be even better to preserve SEO of the main moz.org website. To keep moving forward and making incremental progress, my recommendation is to use a subdomain and then transition to a directory after IT has a database infrastructure setup for Bedrock.

Comment 5

7 years ago
(In reply to Fred Wenzel [:wenzel] from comment #3)
> (In reply to mcbmoz from comment #1)
> > Is there a reason we need to move to a sub-domain?
> 
> Yes, technical necessity. IT can't currently deploy a database-backed
> mozilla.org for us, and the careers page needs a database, so we pulled that
> component out into a separate app for now to unblock the process.
> 
> Once bedrock is up and running and IT can provide the infrastructure to back
> this part of the site out of various data centers, I see no problem with
> moving it back into bedrock (in fact, I'd prefer that), but for now, we
> can't.
> 
> As far as SEO goes, Google and friends recognize redirects, so we should be
> fine with the current setup and be able to pull careers back into a
> subdirectory later to no ill effect.
> 
> (In reply to John Slater from comment #2)
> > Also, why is bug 712331 private?
> 
> It's an IT push bug, those are private by default as they contain server
> names, settings, passwords etc. Christie CCed you on it.

Fred, Thanks for helping us understand the short-term need in using a subdomain, and glad we can move this back to the main domain as a directory after the site migrated to Bedrock.

Comment 6

7 years ago
+1 to moving this back to the root mozilla.org/careers domain with Bedrock - using a separate website just for careers seems to go against the One Mozilla and does little to strengthen our root domain: mozilla.org.
Blocks: 604247
Component: www.mozilla.org/firefox → www.mozilla.org
QA Contact: www-mozilla-com → www-mozilla-org
Flags: in-testsuite?
Can we also add a redirect for http://www.mozilla.org/en-US/about/careers.html ? Or is there a better approach?
(Reporter)

Comment 8

7 years ago
Agreed, I think it makes sense to redirect that particular URL as well.

Updated

7 years ago
Assignee: nobody → server-ops
Component: www.mozilla.org → Server Operations: Web Operations
Flags: in-testsuite?
Product: Websites → mozilla.org
QA Contact: www-mozilla-org → cshields
Version: unspecified → other
We would like to put these redirects in place 2/3 8am, if possible.
Whiteboard: [2/3 8:00 PST]

Comment 10

7 years ago
I should be around to do this. If someone would like to check this redirect in to the proper SVN repo (James / Fred / etc), we can deploy it tomorrow. As of a couple hours ago www.mozilla.org is no longer auto-deploying (temporarily), so IT will need to be around to push the button... but it's probably best done in an .htaccess file that webdev maintains. Let us know when that's good to go and we can deploy it out.
Assignee: server-ops → nobody
Component: Server Operations: Web Operations → www.mozilla.org
Product: mozilla.org → Websites
QA Contact: cshields → www-mozilla-org
(Reporter)

Comment 11

7 years ago
jlongster, can you put those changes into htaccess? Remember the URL in comment 7 too. I can do it too, but you start work a few hours earlier than me ;)
(Reporter)

Comment 12

7 years ago
Jake: I think careers.mozilla.com (not: .org) is forwarded elsewhere. We might need your help with that one tomorrow.
(Assignee)

Comment 13

7 years ago
Oh yeah! I can do it.
(Assignee)

Comment 14

7 years ago
/careers is redirect in r101063
Whiteboard: [2/3 8:00 PST] → [2/3 8:00 PST] r=101063 b=trunk
(Assignee)

Comment 15

7 years ago
for some reason I can't get /about/careers to redirect but I'll try to get that in minute
(Assignee)

Updated

7 years ago
Assignee: nobody → jlong
(Reporter)

Comment 16

7 years ago
Hold on, is about/careers/ even used anywhere? I think what's used is about/careers.html .
(Assignee)

Comment 17

7 years ago
(In reply to Fred Wenzel [:wenzel] from comment #16)
> Hold on, is about/careers/ even used anywhere? I think what's used is
> about/careers.html .

I think those are the same urls to Apache (about/careers automatically looks for .html and .php files). Maybe the trailing slash doesn't work.

All in all, that redirect seems to now be working too. Must have been caching. 

Please test on http://www-dev.allizom.org/ and I'll roll it out once verified.
Keywords: qawanted
[10:45:55.550] GET https://www-dev.allizom.org/careers [HTTP/1.1 302 Found 112ms]
[10:45:55.674] GET http://careers.mozilla.org/en-US/ [HTTP/1.1 200 OK 6496ms]

What's the other case to test?
(In reply to Stephen Donner [:stephend] from comment #18)
> [10:45:55.550] GET https://www-dev.allizom.org/careers [HTTP/1.1 302 Found
> 112ms]
> [10:45:55.674] GET http://careers.mozilla.org/en-US/ [HTTP/1.1 200 OK 6496ms]
> 
> What's the other case to test?

The other case is:

http://www-dev.allizom.org/about/careers 302'ing to:

[10:51:52.939] GET http://careers.mozilla.org/en-US/ [HTTP/1.1 200 OK 6712ms]
(Assignee)

Comment 20

7 years ago
I fixed /about/careers.html and made them 301 redirects. Any final testing? I can push it out soon.
(Reporter)

Comment 21

7 years ago
The redirect in comment 20 works too. Thanks!
(Assignee)

Comment 22

7 years ago
pushed live in r101068
(Assignee)

Updated

7 years ago
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Assignee)

Comment 23

7 years ago
oops, missed a redirect, pushed in r101077
(Reporter)

Comment 24

7 years ago
If I were pedantic, I'd ask you to escape the period in "careers.html" so that this:

http://www-dev.allizom.org/about/careersFhtml

... still 404s, but I'll let that one slide ;)
(Assignee)

Comment 25

7 years ago
(In reply to Fred Wenzel [:wenzel] from comment #24)
> If I were pedantic, I'd ask you to escape the period in "careers.html" so
> that this:
> 
> http://www-dev.allizom.org/about/careersFhtml
> 
> ... still 404s, but I'll let that one slide ;)

If I were pedantic, I'd fix it in r101079
Whiteboard: [2/3 8:00 PST] r=101063 b=trunk → [2/3 8:00 PST] r=101079 b=trunk
Verified redirect to http://careers.mozilla.org/en-US/
Status: RESOLVED → VERIFIED
Keywords: qawanted
(Assignee)

Comment 27

7 years ago
and push it in r101081
Status: VERIFIED → RESOLVED
Last Resolved: 7 years ago7 years ago
Verified FIXED (last 2 remaining items) in prod:

[13:14:07.138] GET http://www.mozilla.org/en-US/about/careers.html [HTTP/1.1 301 Moved Permanently 60ms]
[13:14:07.204] GET http://careers.mozilla.org/en-US/ [HTTP/1.1 200 OK 349ms]
[13:15:49.001] GET http://www.mozilla.org/en-US/about/careersFhtml [HTTP/1.1 404 Not Found 67ms]
Status: RESOLVED → VERIFIED
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.