Bugfix: automatically detect url type generation for varnish#657
Merged
dbu merged 1 commit intoJun 8, 2026
Merged
Conversation
Contributor
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
2 participants
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.
Dear @dbu,
I now stumbled upon a bug where
generate_url_typemust be set if you're using Varnish andproxy_client.varnish.http.base_urlis set. This is because the extension only takesproxy_client.[client].base_urlinto account, while Varnish client usesproxy_client.varnish.http.base_url(lacking "http" in array selector).This PR fixes the automatic absolute/relative path generation if you use a combination of Varnish + custom base URL.