Launchpad itself

Non-existent subdomains-of.launchpad.net return HTTP 500, SSH timeout

Bug #74816 reported by Diogo Matsubara
38
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Tom Haddon

Bug Description

Steps to reproduce:
1. Open https://foo.launchpad.net
2. Receive a 500 Internal Server Error

Or:
1. sftp -v <email address hidden>
2. Wait while ssh hangs

Such domains should be reported as not existing.

See original description
Christian Reis (kiko)
Changed in launchpad:
assignee: nobody → stevea
importance: Undecided → Critical
Revision history for this message
Rouben (rouben) wrote :

Confirmed here; bug reproducible.

Changed in launchpad:
status: Unconfirmed → Confirmed
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

<SteveA> it's not critical
<SteveA> I'd say it's medium

Changed in launchpad:
importance: Critical → Medium
Revision history for this message
Christian Reis (kiko) wrote :

Reducing to medium since we have established it only happens in production in restricted situations.

This does affect people running a launchpad development instance when the virtualhostnames set in the config file doesn't match to a hostname used to hit on port 8086.

It is trivial to reproduce.

Changed in launchpad:
importance: Medium → Low
Diogo Matsubara (matsubara)
Changed in launchpad:
importance: Low → Medium
Revision history for this message
Rouben (rouben) wrote : Re: Return HTTP 404 error, not 500, for non-existent domains

Confirmed with the new version of Launchpad as well, this issue is still manifesting itself.

Test used: https://foo.launchpad.net

Revision history for this message
Christian Reis (kiko) wrote :

Why is this assigned to Steve?

Revision history for this message
Christian Reis (kiko) wrote :

We don't want to be 500ing all over the place if it's not an expensive fix. :-)

Changed in launchpad:
assignee: stevea → mthaddon
importance: Medium → High
Revision history for this message
Tom Haddon (mthaddon) wrote :

I've tested this and the error is in LP, not in apache. In other words, we just pass on all *.launchpad.net requests to the app servers, so it's up to the app server to return the appropriate HTTP error code, not Apache.

Therefore, I'm not sure I'm the best person to take care of it - sounds like a code change that I'm not familiar with. Is it possible to re-assign this to someone who could take care of it?

Revision history for this message
Joey Stanford (joey) wrote :

reassigning to Kiko for disposition

Changed in launchpad:
assignee: mthaddon → kiko
Christian Reis (kiko)
Changed in launchpad:
assignee: kiko → stub
Revision history for this message
Stuart Bishop (stub) wrote :

We have decided to drop the wildcard DNS, as it is causing issues with other protocols we are now supporting on the launchpad.net domain (such as sftp/ssh for bzr).

Changed in launchpad:
status: Confirmed → Won't Fix
Matthew Paul Thomas (mpt)
description: updated
Changed in launchpad:
status: Won't Fix → Confirmed
Stuart Bishop (stub)
Changed in launchpad:
assignee: stub → nobody
Diogo Matsubara (matsubara)
Changed in launchpad:
assignee: nobody → mthaddon
Revision history for this message
Tom Haddon (mthaddon) wrote :

Compiling list of host names...

Changed in launchpad:
status: Confirmed → In Progress
Revision history for this message
Tom Haddon (mthaddon) wrote :

Wildcard DNS has been removed. Incorrect hostnames will now be not found.

Changed in launchpad:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.