Closed Bug 1548830 Opened 7 years ago Closed 7 years ago

Token page has incorrect usage example

Categories

(Socorro :: Webapp, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jwhitlock, Assigned: jwhitlock)

Details

Attachments

(1 file)

On https://crash-stats.mozilla.com/api/tokens/ (login required), there is an example of token usage:

curl -H "Auth-Token: 58af2acef8a74dbca9580e2bb8ba9c9a" https://crash-stats.mozilla.com/api/RawCrash/?uuid=fb27d0f3-db8e-4835-9311-288bb0170829

The query parameter should be crash_id, not uuid:

curl -H "Auth-Token: 58af2acef8a74dbca9580e2bb8ba9c9a" https://crash-stats.mozilla.com/api/RawCrash/?crash_id=fb27d0f3-db8e-4835-9311-288bb0170829

The Python example has a similar issue. It also uses an 'x' in the token, to ensure it is not a legitimate hexadecimal string.

A stretch goal would be to make it a working rather than sample example, using the user's token with "View Raw Dumps" and a valid crashid, using jQuery to hide the examples by default. This probably makes the fix more complex than needed.

The initial PR is the minimal version of the fix, just uuidcrash_id.

Assignee: nobody → jwhitlock

I just pushed this to prod and verified it's correct there now. Marking as FIXED.

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: