Skip to content

Identify identity-rail requests with a User-Agent - #18

Merged
codeyogi911 merged 1 commit into
mainfrom
fix/identity-user-agent
Aug 8, 2026
Merged

Identify identity-rail requests with a User-Agent#18
codeyogi911 merged 1 commit into
mainfrom
fix/identity-user-agent

Conversation

@codeyogi911

Copy link
Copy Markdown
Owner

Shopify's edge returns 403 to requests without a User-Agent, and a Workers-runtime fetch sends none — so customer-account discovery (and the whole sign-in flow) failed in production while working from curl and browsers. One change: every identity-module request now carries an identifying agent.

Verified live against the real store locally: /auth/shopify/start now 302s to the hosted Shopify login with correct client, scope, and PKCE. npm run check green.

🤖 Generated with Claude Code

Shopify's edge rejects requests without a User-Agent header with a 403, and
a Workers-runtime fetch sends none by default, so discovery — and with it the
whole sign-in flow — failed in production while working from a browser or
curl. Send an identifying agent on every identity request.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@codeyogi911
codeyogi911 enabled auto-merge (squash) August 8, 2026 08:32
@codeyogi911
codeyogi911 merged commit 7570826 into main Aug 8, 2026
5 checks passed
@codeyogi911
codeyogi911 deleted the fix/identity-user-agent branch August 8, 2026 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant