307703 - pfs.mozilla.org is issuing redirections etc. to 192.168.0.201

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Ian Jackson]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Debian/1.7.8-1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Debian/1.7.8-1

pfs.mozilla.org us issuing URLs containing the IP address 192.168.0.201, which
is presumably somewhere inside the mozilla facilities centre network(s), since
it's a non-globally-routeable RFC1918 address which no-one else can see.

Reproducible: Always

Steps to Reproduce:
Two easy ways:

1. Install firefox 1.0.6* from Ubuntu Breezy.
2. tcpdump it
3. Select a site with flash and attempt to download the plugin.  You will see
firefox attempt to make a connection to 192.168.0.201:443.

Second way:
1. Visit https://pfs.mozilla.org/developers/index.php
2. Select Create an Account
3. Fill in an email address etc.
4. Observe that the email you get contains a string like this:
To activate your account, click the link below or copy and paste the whole thing
into your browsers location bar:
https://192.168.0.201/developers/createaccount.php?function=confirmaccount&email=...
Actual Results:  
Firefox attempts to connect to an RFC1918 address.  Eventually it times out and
the plugin download fails.  (The error message is very poor too.)


Expected Results:  
If there was going to be a redirect, it should go to the right place.

The emails re new developer accounts should have correct URLs.

I have marked this bug `Blocker' because I am the person responsible for Firefox
for Ubuntu (the Debian-derived Linux distribution) and it is preventing me
investigating various plugin-related bug reports I have in the Ubuntu bugzilla
(http://bugzilla.ubuntu.org, packages firefox and mozilla-firefox).

Feel free to change the severity if you like but it seems pretty bad to me !

Comment 1

[Dave Miller [:justdave]]

https://pfs.mozilla.org/developers/ should not work at all.  The fact that
you're getting a page at that address is a bug.  I suspect the redirect to an IP
is related.

Yep, indeed, the proxy server was not passing the hostname through to the
back-end server, which was then applying the wrong vhost to the connection, and
the proxy was then flubbing the rewrites on the redirected hostname on the way
back out as well.  Both have been fixed, and it should work correctly now.

jst: I'd appreciate double-checking to make sure PFS still works.  I'm confused
why it actually worked before.

Comment 2

[Johnny Stenback (:jst)]

Seems to still be working just fine.