Fix Launch VIP Discord mixed content#14520
Merged
Merged
Conversation
|
raymondjacobson
changed the title
raymondjacobson
changed the title
raymondjacobson
added a commit
that referenced
this pull request
Jul 13, 2026
## Summary - send the Discord JWT request as `POST /request_discord_code` with a JSON body instead of query params - encode the Discord OAuth `state` payload before appending it to the OAuth URL ## Context PR #14520 fixed the mixed-content issue by switching the production Discord bot URL to HTTPS. This follow-up moves signature/message transport out of the URL and into a JSON request body, avoiding URL length and query logging concerns. ## Companion PRs - Bot POST support: AudiusProject/discord-audio-bot#24 - k8s JWT secret wiring: AudiusProject/audius-k8s#514 ## Rollout Merge/deploy after the bot supports POST. Recommended order: 1. Create/set `discord-bot-JWT_SECRET` in GCP Secret Manager. 2. Merge/apply the k8s secret wiring PR. 3. Merge/deploy the bot POST-support PR. 4. Merge/deploy this apps PR. ## Test plan - `git diff --check` Could not run local Vitest because this worktree has no installed `node_modules`, so `vitest` is unavailable (`sh: vitest: command not found`).
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.
Summary
Diagnosis
The Launch VIP Discord flow was blocked by the browser because
https://audius.co/rewardstried to fetchhttp://discord.audius.co/request_discord_code. The HTTP endpoint redirects to HTTPS, but browsers block mixed-content requests before following that redirect.Follow-ups
Test plan
git diff --check -- packages/web/src/services/env/env.prod.ts packages/web/src/services/env/env.prod.test.tscurl -sSIL --max-time 10 https://discord.audius.co/request_discord_codereturns an app-level response over HTTPS, confirming the HTTPS endpoint is reachableCould not run the focused Vitest test locally because this worktree had no installed
node_modules, sovitestwas unavailable (sh: vitest: command not found).