Switch to new api.daxformatter.com endpoint and remove redirect handling#23
Merged
Conversation
Update service URIs to use the new API endpoint directly. The old www.daxformatter.com URLs are still online but permanently redirect (301) to the new host. We update the service URIs to point directly to the new endpoint and remove the redirect-resolution machinery that was needed to follow those redirects at runtime.
The _formatSemaphore that serialized all format calls one at a time was originally introduced to guard the redirect-resolution logic. Now that the library calls the stable api.daxformatter.com endpoint directly, there is nothing to serialize: HttpClient is thread-safe by design and concurrent requests are safe. AllowAutoRedirect is restored to the HttpClientHandler default (true) so any future redirect is followed transparently without custom handling. ReadAsStringAsync replaces the synchronous StreamReader.ReadToEnd so the response body is read fully asynchronously.
albertospelta
added a commit
to albertospelta/semantic-link-labs
that referenced
this pull request
Jun 11, 2026
Migrate from `daxformatter.azurewebsites.net` to `api.daxformatter.com` as per sql-bi/DaxFormatter#23. The old domain issues permanent 301 redirects to the new host. The new `api.daxformatter.com` domain also drops the `/daxformatter/` segment from the path: `/api/daxformatter/daxtextformatmulti`
albertospelta
added a commit
to albertospelta/DaxStudio
that referenced
this pull request
Jun 11, 2026
Migrate to api.daxformatter.com and updated path /api/daxtextformat per sql-bi/DaxFormatter#23. Remove the now-obsolete redirect-following and connection-priming code as the new endpoint is the direct API host.
albertospelta
added a commit
to albertospelta/TabularEditor
that referenced
this pull request
Jun 11, 2026
This pull request updates DaxFormatterProxy to use the new DAX Formatter API endpoint, following the migration in [sql-bi/DaxFormatter#23](sql-bi/DaxFormatter#23). The service moved from `www.daxformatter.com/api/daxformatter/` to the new official API host `api.daxformatter.com/api/`. The new `api.daxformatter.com` host is the direct API endpoint and no longer issues a redirect, so all the redirect-following and connection-priming code has been removed.
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.
This pull request updates the API endpoints used for formatting requests switching to the new API domain.
API Endpoint Updates
DaxFormatterSingleRequestandDaxFormatterMultipleRequestto use the newhttps://api.daxformatter.comdomain instead ofhttps://www.daxformatter.com.Refactoring and Simplification
SemaphoreSlim) and related logic for synchronizing service URI initialization. Now, the service URI is taken directly from the request object.HTTP Client Handler Change
AllowAutoRedirect = false;.