Conversion to Varnish 4.0 #11
Closed
Conversation
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.
Here is a conversion to Varnish 4.0 VMOD format.
I've just applied the same changes Varnish made to their own vmods, and removed
VARNISHSRCreference in the readme.The test pass but I haven't tried myself (I've made the conversion to try it on my Varnish v4 platform, which could take a while).
You'll probably want to create a new branch for this new version or for the v3 before merging: as V4 VMODs aren't compatible with Varnish 3, it's necessary to maintain both versions, but backports are easy (most changes can be merged as is in both versions).