Closed Bug 631341 Opened 10 years ago Closed 10 years ago

[post-crash] Implement crash-signature API

Categories

(support.mozilla.org :: Knowledge Base Software, task, P1)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jsocol, Assigned: jsocol)

Details

Targeting this for release (probably a 2.5.1) the 2nd full week of March (15 or 17).


Input (one of):

 GET /some/url/<signature>
 GET /some/url?signature=<signature>

Output if article found:

 HTTP/1.0 200 OK
 Content-type: text/plain
 Cache-control: max-age=86400

 http://support.mozilla.com/...

Output if article not found:

 HTTP/1.0 404 Not Found
 Cache-control: max-age=86400

Output if no-change (with conditional get):

 HTTP/1.0 304 Not Modified

Output on failure:

 HTTP/1.0 5xx

Consumers should throttle requests after a failure.
Target Milestone: 2011Q1 → 2.6.1
Target Milestone: 2.6.1 → 2.6.2
https://github.com/jsocol/kitsune/compare/ebbd99c8%5E...78317b2d

This will go out on March 15th, barring anything crazy like a Firefox release.

QA: You'll need to create some data to test this:

1) In the admin, go to Postcrash > Signatures.
2) Create a new Signature object and link it to some document.

Then these are the requests and their responses:

GET /postcrash
HTTP/1.0 400 Bad Request

GET /postcrash?s=non-existent
HTTP/1.0 404 Not Found

GET /postcrash?s=<signature from step 2>
HTTP/1.0 200 OK
http://<host>/kb/<slug from document in step 2>


In all cases Content-type is text/plain. On at least 200 OK (and maybe 404) it should send 24-hour caching headers.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Verified by adding signature to desktop-mobile, and going here: https://support-release.allizom.org/postcrash?s=this%20is%20a%20new%20test%20signature
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.