Revert browser headers on login POST and MFA verify#212
Conversation
The login POST and MFA verify are mobile API endpoints that expect GCM-iOS user agent (set on the session). Sending browser headers on these caused Garmin to reject with 401. Browser headers should only be on page requests (sign-in, embed) — not on the JSON API calls. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughRemoves the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #212 +/- ##
==========================================
- Coverage 99.91% 99.91% -0.01%
==========================================
Files 68 68
Lines 3567 3566 -1
==========================================
- Hits 3564 3563 -1
Misses 3 3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
0.7.7 regression: the browser UA on the login POST caused Garmin to reject with 401. The login POST and MFA verify are mobile API endpoints that expect
GCM-iOS-*, not a browser UA.Browser headers should only be on page requests (sign-in, embed) — the JSON API calls use the default session UA.
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit
Refactor
Chores