fix(storefront): Register customer device sent an empty duplicate auth header - #39
Merged
Merged
Conversation
…h header
The request carried BOTH `Customer-Token: {{customer_token}}` and a second,
empty `customer-token: ""`. HTTP header names are case-insensitive, so the empty
one collided with the real token and the endpoint answered "Not authorized to
register device for cutomer" — the customer never resolved.
Its body was also empty, so even with a valid token it had no token or platform
to register. It now sends {{device_token}}, which the contract run already
injects for the FleetOps driver device requests, and platform "ios".
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two faults in one request.
A duplicate, empty auth header. It carried both
Customer-Token: {{customer_token}}and a secondcustomer-token: "". HTTP header names are case-insensitive, so the empty one collided with the real token and the endpoint answered "Not authorized to register device for cutomer" — the customer never resolved. The empty duplicate is removed.An empty body.
content: "", so even with a valid token there was notokenorplatformto register. It now sends{{device_token}}— already injected by the contract run for the FleetOps driver device requests — andplatform: "ios".(The typo in the API's error message, "cutomer", is left alone: changing it would be a user-visible string change unrelated to this fix.)
🤖 Generated with Claude Code