Closed
Bug 1353756
Opened 7 years ago
Closed 7 years ago
Treestatus HTTP 500s for unknown repositories
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Unassigned)
References
Details
$ curl -I https://treestatus.mozilla-releng.net/trees/fxapom HTTP/1.1 500 Internal Server Error Server: Cowboy Date: Wed, 05 Apr 2017 14:41:34 GMT Connection: keep-alive Content-Type: text/html Content-Length: 141 Via: 1.1 vegur $ curl -I https://treestatus.mozilla-releng.net/trees/ HTTP/1.1 500 Internal Server Error Server: Cowboy Date: Wed, 05 Apr 2017 14:45:23 GMT Connection: keep-alive Content-Type: text/html Content-Length: 141 Via: 1.1 vegur In addition, the HTTP 500 is missing the CORS header, so consumers like Treeherder don't see the HTTP 500 but the equivalent of a network timeout instead: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://treestatus.mozilla-releng.net/trees/fxapom. (Reason: CORS header 'Access-Control-Allow-Origin' missing).
Reporter | ||
Comment 2•7 years ago
|
||
Fixed by: https://github.com/mozilla-releng/services/commit/51d7e0c3ab3ce9b556d5eea592810553b70e214e
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Comment 3•7 years ago
|
||
:emorley: This landed in mozilla-releng/services master, but I'm waiting with releasing it until Tue (after holidays).
Comment 4•7 years ago
|
||
:emorley: this was now deployed
Assignee | ||
Updated•2 years ago
|
Component: Applications: TreeStatus → General
You need to log in
before you can comment on or make changes to this bug.
Description
•