Fix Microsoft Foundry URL path mode for proxy hosts#6180
Open
jewoodev wants to merge 1 commit into
Open
Conversation
Signed-off-by: jewoodev <jewoos15@naver.com>
jewoodev
changed the title
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.
Why: When
spring.ai.openai.microsoft-foundry=trueis combined with an enterprise proxybase-url, embedding and chat requests miss the/openai/deployments/{deployment}path and the?api-version=...query, returning 404. The openai-java SDK keepsAzureUrlPathMode.AUTO, which classifies hosts via an Azure-domain whitelist — proxy hosts fall through toNON_AZUREand the SDK skips Azure URL shaping, even when Spring AI has already resolved the provider asMICROSOFT_FOUNDRY.How: This forwards that decision to the SDK: when the provider is
MICROSOFT_FOUNDRY, the client builder is givenAzureUrlPathMode.UNIFIEDif the base URL ends with/openai/v1, andAzureUrlPathMode.LEGACYotherwise. The path mode is set before credential selection, so the same decision reaches every authentication path. Behavior worked in 1.1.0-M3 and regressed after the SDK migration.Test:
OpenAiSetupTestscovers sync/async proxy hosts, the unified endpoint, an explicitCredentialinjection, and non-Foundry baselines (OpenAI and GitHub Models) that keepAUTO. Verified with./mvnw package.Closes #6060