Closed
Bug 815633
Opened 12 years ago
Closed 12 years ago
mx-live checking with DNS timeout should return 504, not 500
Categories
(Infrastructure & Operations Graveyard :: WebOps: Labs, task)
Infrastructure & Operations Graveyard
WebOps: Labs
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: mkaply, Assigned: gozer)
Details
Sorry, I have no idea if this is the right bug component.
Thunderbird uses the mx-live.mozillamessaging.com server do do mx server checks for domains.
I've found a case where it fails in a strange way:
https://mx-live.mozillamessaging.com/dns/mx/eb.de
causes an internal server error.
https://mx-live.mozillamessaging.com/dns/mx/web.de works fine
https://mx-live.mozillamessaging.com/dns/mx/b.de works fine.
Reporter | ||
Updated•12 years ago
|
Summary: mz-live checking for eb.de causes an internal server error → mx-live checking for eb.de causes an internal server error
Comment 1•12 years ago
|
||
My actual result:
The page takes 2 minutes to load, then results in a "Service unavailable" webpage.
This is just the DNS server of eb.de not responding. When I do
dig mx eb.de
it also stalls for 1 minute, then dig says "connection timeout".
So, the webservice reacts properly. Just the return code 500 is wrong, which is by definition an intenal server error, which this is not. I would change the return code to "504 Gateway timeout", because that seems to be *exactly* out case here.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
"
10.5.5 504 Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
Note: Note to implementors: some deployed proxies are known to
return 400 or 500 when DNS lookups time out.
"
Good spec.
Summary: mx-live checking for eb.de causes an internal server error → mx-live checking with DNS timeout gives an internal server error
Updated•12 years ago
|
Summary: mx-live checking with DNS timeout gives an internal server error → mx-live checking with DNS timeout should return 504, not 500
Updated•12 years ago
|
Severity: normal → minor
Comment 2•12 years ago
|
||
This should live in mozilla.org now.
Assignee: nobody → server-ops
Product: Mozilla Messaging → mozilla.org
QA Contact: shyam
Updated•12 years ago
|
Assignee: server-ops → server-ops-labs
Component: Server Operations → Server Operations: Labs
QA Contact: shyam → zandr
Comment 3•12 years ago
|
||
Gozer, no idea where this lives or how this can be patched/fixed.
Assignee: server-ops-labs → gozer
Assignee | ||
Comment 4•12 years ago
|
||
Landed the code change on github https://github.com/gozer-mozilla/http-mx/commit/64c2b05d30ac131cf82dda22c598f5b172692fb7
The code itself runs on a labs VM at the moment, I'll patch that one up shortly.
Assignee | ||
Comment 5•12 years ago
|
||
Deployed
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Infrastructure & Operations
Updated•9 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•