-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCL include +glob with relative path is not working #4249
Labels
Comments
bugwash agrees that with |
walid-git
added a commit
to walid-git/varnish-cache
that referenced
this issue
Jan 7, 2025
@masarlabs can you give #4250 a try ? |
walid-git
added a commit
to walid-git/varnish-cache
that referenced
this issue
Jan 7, 2025
walid-git
added a commit
to walid-git/varnish-cache
that referenced
this issue
Jan 7, 2025
We preivously called glob() on the included file name regardless of whether it was an absolute or relative path. As a result, relative paths were not appended to vcl_path elements before checking if the glob expression matched anything. It is not possible to (re)use VFIL_searchpath here, since VFIL_searchpath uses access() to check that the file exists, and that would fail in this case. Fixes: varnishcache#4249
walid-git
added a commit
to walid-git/varnish-cache
that referenced
this issue
Jan 7, 2025
Compiled
Version
Test
No error, it seems to work. |
Thanks for confirming. I will keep the issue open until a fix (#4250 or other) is merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
I created a minimal default.vcl that includes an empty file
then test the code with
it should go without error
Current Behavior
the first two includes work as expected, but the last one says
Possible Solution
I think that current directory is not set correctly because it works with full path.
Steps to Reproduce (for bugs)
No response
Context
Cannot use relative path in vcl
Varnish Cache version
varnishd (varnish-7.6.1 revision c3d5882)
Operating system
alpine 3.21.0
Source of binary packages used (if any)
No response
The text was updated successfully, but these errors were encountered: