- 17 Jun, 2025 1 commit
-
-
Nils Goroll authored
Introduced in b2d216fd
-
- 23 May, 2025 1 commit
-
-
Thibaut Artis authored
-
- 12 May, 2025 4 commits
-
-
Thibaut Artis authored
Migrate to VCDK See merge request uplex/varnish/libvmod-re2!3
-
Thibaut Artis authored
Since VC 7.7, vmodtool.py generates a file that must be taken into account in Makefile.am https://varnish-cache.org/docs/trunk/whats-new/upgrading-7.7.html
-
Thibaut Artis authored
Refactoring of this VMOD so that it corresponds to the schema described in https://git.sr.ht/~dridi/vcdk
-
Thibaut Artis authored
Abseil, on which re2 depends now requires building for C++17.
-
- 10 May, 2024 1 commit
-
-
Geoff Simmons authored
Fixes gitlab issue #1.
-
- 01 Aug, 2023 1 commit
-
-
Nils Goroll authored
-
- 08 Dec, 2022 1 commit
-
-
Nils Goroll authored
-
- 01 Dec, 2022 1 commit
-
-
Nils Goroll authored
-
- 09 Nov, 2022 1 commit
-
-
Nils Goroll authored
-
- 27 Apr, 2022 2 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
-
- 13 Sep, 2021 2 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
-
- 07 Jun, 2021 1 commit
-
-
Geoff Simmons authored
-
- 22 Apr, 2021 5 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
- Changed error handling -- VCL failure for unrecoverable errors. - .compile() is now unnecessary and deprecated. - Addition of .subroutine() and .check_call(). - Update the REQUIREMENTS and compatibility statements. - Fix some typos noticed along the way.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 21 Apr, 2021 4 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
.compile() is still legal, but unnecessary and will be deprecated.
-
- 20 Apr, 2021 2 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
Up to now we have emitted sentinel values for this class of errors, a relic of the time before VCL failure was introduced, when the VMOD was first developed. This may lead to fatal errors going unnoticed. These are the sorts of errors that should fail fast in development and testing, and never make it into production. We were already using VCL failure for the integer() method, since there is no sentinel integer. VCL failure is now invoked for these errors: - any regex compilation failure - all out of workspace errors - compile() or add() called in any VCL subroutine besides vcl_init - match() called for a set that was not compiled - failures reported by the RE2 lib for: match(), backref(), namedref(), the rewrite operations (sub, suball and extract), cost(), quotemeta() - numeric index reference for a set object (n parameter) that is out of range (greater than the number of patterns in the set) - functions and methods that require a previous successful match operation (with information stored in priv_task) when there was no prior match, or the previous macth failed. - use of select=UNIQUE when more than one pattern in a set matched - numeric (by index) or "associative" (after match) retrieval of an object for a set when no such object was saved in the constructor: strings, backends, regexen, etc - any of the following are undefined (NULL): fallbacks; patterns for regex functions (which are compiled at runtime); the text and rewrite parameters for the rewrite operations; name parameter for namedrefs - also if the named parameter for namedrefs is the empty string - backref number out of range (greater than the number of backrefs) - backref or namedref attempted without a prior match - backref or namedref when never_capture=true in the contructor - low-level failures reported by RE2 (eg cannot determine the number of backref groups). Most of these are possible, since the call returns an error status, but I have never seen them happen. VTC tests have been revised for the new error handling, which changes quite a bit in this commit. While we're here, use backend None in the tests where appropriate. Note that "bad_ip" backends are still necessary to test methods and functions that retrieve backends (numeric or associative references for sets). Error reporting is now done with VCL_fail(), so we get rid of the errmsg() function, and with it the re2.c source (since that was all there was in re2.c).
-
- 10 Feb, 2021 4 commits
-
-
Nils Goroll authored
use VRT_Fail() instead This change should be improved by refactoring error handling
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
- 28 Jan, 2021 1 commit
-
-
Geoff Simmons authored
-
- 30 Dec, 2020 1 commit
-
-
Geoff Simmons authored
-
- 09 Dec, 2020 1 commit
-
- 01 Sep, 2020 1 commit
-
-
Geoff Simmons authored
-
- 13 Aug, 2020 1 commit
-
-
Geoff Simmons authored
-
- 12 Aug, 2020 2 commits
-
-
Geoff Simmons authored
The rst source has apparently become too large for gitlab web sites to be able to render it. So we just go with markdown, in the hopes that gitlab can better cope with it. It's not an error if you don't have pandoc installed, but then README will not be kept up to date with the docs in vcc.
-
Geoff Simmons authored
Since 2020-06-01, backrefs fail if numbered higher than the highest backref actually captured- Previously, re2 returned the empty string. I believe that these tests will now pass for both current and earlier versions.
-
- 10 Dec, 2019 1 commit
-
-
Nils Goroll authored
-
- 13 Nov, 2019 1 commit
-
-
Nils Goroll authored
-