Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

UAID's supplied with dashes should be invalidated #519

Closed
bbangert opened this issue Jul 15, 2016 · 0 comments
Closed

UAID's supplied with dashes should be invalidated #519

bbangert opened this issue Jul 15, 2016 · 0 comments
Assignees
Labels

Comments

@bbangert
Copy link
Member

Because /v1 and /v2 URL's all return uuid's with no dashes, old FF clients have endpoints generated that cannot be valid. As such we should invalidate the UAID upon connect if it has a dash in it, and treat it as invalid.

@bbangert bbangert added the bug label Jul 15, 2016
@bbangert bbangert added this to the PUSHSVC-0: quality milestone Jul 15, 2016
jrconlin added a commit that referenced this issue Jul 15, 2016
Older UAIDs contain invalid characters and should be rejected.

Closes #519
jrconlin added a commit that referenced this issue Jul 15, 2016
Older UAIDs contain invalid characters and should be rejected.

Closes #519
@jrconlin jrconlin self-assigned this Jul 15, 2016
jrconlin added a commit that referenced this issue Jul 15, 2016
Older UAIDs contain invalid characters and should be rejected.

Closes #519
jrconlin added a commit that referenced this issue Jul 16, 2016
Older UAIDs contain invalid characters and should be rejected.

Closes #519
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants