Closed
Bug 957503
Opened 10 years ago
Closed 10 years ago
Change "Browser-ID" to "BrowserID" in tokenserver Authorization header?
Categories
(Cloud Services Graveyard :: Server: Token, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rfkelly, Unassigned)
References
Details
(Whiteboard: [qa-])
Trivial API nit: the canonical spelling of the protocol name is "BrowserID" [1], not "Browser-ID" as currently used in the tokenserver Authorization header. Should we change it while we can in the interests of consistency, or is that just pointless API churn? Nick and Alexis, thoughts? [1] https://developer.mozilla.org/en-US/Persona/Glossary
Comment 1•10 years ago
|
||
(In reply to Ryan Kelly [:rfkelly] from comment #0) > Trivial API nit: the canonical spelling of the protocol name is "BrowserID" > [1], not "Browser-ID" as currently used in the tokenserver Authorization > header. > > Should we change it while we can in the interests of consistency, or is that > just pointless API churn? Nick and Alexis, thoughts? Meh. There's nothing consistent about BrowserID or Persona anyway. I know from having reverse engineered the data formats :) Also, all the code that says BrowserID* will never change to Browser-ID. If we care, it's trivial to change; but I don't care.
Updated•10 years ago
|
Whiteboard: [qa-]
Reporter | ||
Comment 2•10 years ago
|
||
"meh" it is; closing
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 4•10 years ago
|
||
We're mucking around with this endpoint anyway in Bug 959441, let's clean this up while we're at it.
Status: VERIFIED → REOPENED
Resolution: WONTFIX → ---
Reporter | ||
Comment 5•10 years ago
|
||
This is done, and is what will go into production. I've patched the current dev server to accept both forms so that client code doesn't have to coordinate the fix with a server rollout.
Reporter | ||
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Comment 6•10 years ago
|
||
OK. I assume this will automatically propagate into Stage and Production.
Status: RESOLVED → VERIFIED
Updated•1 year ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•