Closed
Bug 1055263
Opened 10 years ago
Closed 10 years ago
update esFrontLine in production
Categories
(bugzilla.mozilla.org :: Infrastructure, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: ekyle, Assigned: fubar)
References
(Blocks 1 open bug)
Details
Please update the production esFrontLine with the master version found on Github at https://github.com/klahnakoski/esFrontLine/tree/6ffb5358ee554fb40a3bf38eaf7f36b644375d6c
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Comment 1•10 years ago
|
||
I forget if production deployed from PyPi, if so, this code is in the version 1.1.14230
Assignee | ||
Comment 2•10 years ago
|
||
Updated, but appears to be only returning error 400, bad request on testing $ curl https://esfrontline.bugzilla.mozilla.org/public_bugs/bug_version/_search <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <title>400 Bad Request</title> <h1>Bad Request</h1> <p>The browser (or proxy) sent a request that this server could not understand.</p> 2014-08-19 07:22:37,214 - esFrontLine - DEBUG - path: public_bugs/bug_version/_search, request bytes=2375, response bytes=1791 2014-08-19 07:22:38,640 - esFrontLine - DEBUG - path: public_bugs/bug_version/_search, request bytes=246, response bytes=273
Assignee: nobody → klibby
Flags: needinfo?(klahnakoski)
Reporter | ||
Comment 3•10 years ago
|
||
Kendall,
Thanks, it looks good! This patch only enables HEAD requests on /, and that is working as expected. Furthermore charts.mozilla.org (which uses this) is working fine.
> curl -D - -X HEAD http://esfrontline.bugzilla.mozilla.org:80
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(klahnakoski)
Resolution: --- → FIXED
Reporter | ||
Comment 4•10 years ago
|
||
I should have included the response: > curl -D - -X HEAD http://esfrontline.bugzilla.mozilla.org:80 > HTTP/1.0 200 OK > Server: Werkzeug/0.9.6 Python/2.7.3 > content-type: text/plain; charset=UTF-8 > Date: Tue, 19 Aug 2014 14:45:45 GMT > access-control-allow-origin: * > Connection: Keep-Alive > content-length: 0
You need to log in
before you can comment on or make changes to this bug.
Description
•