google-deepmind: add waa-pa & people-pa under clients6.google.com#3708
Open
stupidloud wants to merge 1 commit into
Open
google-deepmind: add waa-pa & people-pa under clients6.google.com#3708stupidloud wants to merge 1 commit into
stupidloud wants to merge 1 commit into
Conversation
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.
What
Add two
*-pa.clients6.google.comsubdomains that current Gemini frontends(both
gemini.google.comandaistudio.google.com) call but the existinggoogle-deepmindlist does not match:full:waa-pa.clients6.google.comfull:people-pa.clients6.google.comWhy
clients6.google.comis Google's shared host for-pa(private API) gRPCendpoints. Different products mount different
*-pasubdomains under it. Theexisting list only covers AI Studio's three
alkali*-paendpoints. ModernGemini frontends additionally call:
google.internal.waa.v1.Waa/Createintegrity-token service. Without it,the Gemini web UI loads but message sends are blocked with region/abuse
errors. This domain is explicitly listed in Google's own Gemini app
firewall allowlist: https://support.google.com/a/answer/15627649
(distinct from the public
people.googleapis.com). Used by Gemini foraccount/profile context and
@mentionfeatures. Documented as"Internal People API" in
Internal People Api Permission Denied google/google-api-javascript-client#608
Why
full:(not a bare suffix)PR #3292 proposes replacing the existing
full:alkali*entries with a bareclients6.google.comsuffix. While simpler, that would also route*.clients6.google.comsubdomains used by Gmail, Drive, Photos,Workspace add-ons, etc. — products that users may want on a different
outbound. Sticking with
full:keeps the list narrowly scoped to Gemini'sknown backends; new Gemini subdomains can be added one at a time as they
are observed in the wild.
Verification
Captured live from a Gemini session: both subdomains appear in DevTools
network traffic and the Gemini "region not supported" errors reported in
issues #2378, #2938 and #3188 go away once these two are routed through the
same outbound as the rest of
google-deepmind.Refs: #2938, #2378, PR #3292