feat(ai-proxy): add anonymous affinity cookie fallback#3574
Open
hongshi1 wants to merge 1 commit intohigress-group:mainfrom
Open
feat(ai-proxy): add anonymous affinity cookie fallback#3574hongshi1 wants to merge 1 commit intohigress-group:mainfrom
hongshi1 wants to merge 1 commit intohigress-group:mainfrom
Conversation
|
gexuancheng seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
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
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.
Ⅰ. Describe what this PR did
Added anonymous affinity cookie fallback for stateful AI APIs in ai-proxy. When x-mse-consumer is absent, the first successful response returns a higress-ai-affinity cookie and subsequent requests use that cookie for stable token selection.
Ⅱ. Does this pull request fix one issue?
fixes #3473
Ⅲ. Why don't you add test cases (unit test/integration test)?
Added provider unit tests and TestConsumerAffinity regression coverage for anonymous cookie fallback.
Ⅳ. Describe how to verify it
Run go test ./provider/... and go test . -run TestConsumerAffinity -count=1 -timeout 60s under plugins/wasm-go/extensions/ai-proxy.
Ⅴ. Special notes for reviews
This change only affects stateful APIs with multiple apiTokens configured and keeps x-mse-consumer as the first-priority affinity key.