Repository navigation
fix(accounts): normalize API key upstream endpoints - #183
Merged
Merged
Conversation
HTExplicit
force-pushed
the
fix/apikey-account-creation
branch
2 times, most recently
from
September 18, 2026 12:08
caa2227 to
88d24f6
Compare
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.
Problem
The admin API-key account form passed a host-only endpoint such as
api2.aigcbest.topto the upstream model-sync preview. The preview rejected it as an invalid URL before account creation, while other paths handled endpoint input differently.Fix
https://...in the account form and in the backend credential/preview path.Validation
go build ./...git diff --check