Commit b0c33f72 by Geoff Simmons

The problem of using vre limits from the Varish params is finally fixed.

parent 7def7624
Pipeline #202 skipped
......@@ -357,14 +357,10 @@ full expression indicated by backref 0. If a ``match`` or
(10 substrings and the full string), then a ``VCL_Error`` message is
emitted to the Varnish log, and the captures are limited to 11.
XXX: the following paragraph is currently not true, bug is under
investigation
Regular expression matching is subject to the same limitations that
hold for standard regexen in VCL, for example as set by the runtime
parameters ``pcre_match_limit`` and ``pcre_match_limit_recursion``.
SEE ALSO
========
......
......@@ -157,12 +157,8 @@ match(VRT_CTX, vre_t *vre, VCL_STRING subject, struct vmod_priv *task)
else
CAST_OBJ(ov, task->priv, OV_MAGIC);
/* XXX: cache_param->vre_limits incorrect?! */
s = VRE_exec(vre, subject, strlen(subject), 0, 0, nov, MAX_OV,
NULL);
#if 0
&cache_param->vre_limits);
#endif
if (s <= VRE_ERROR_NOMATCH) {
if (s < VRE_ERROR_NOMATCH)
VSLb(ctx->vsl, SLT_VCL_Error,
......
......@@ -293,14 +293,10 @@ full expression indicated by backref 0. If a ``match`` or
(10 substrings and the full string), then a ``VCL_Error`` message is
emitted to the Varnish log, and the captures are limited to 11.
XXX: the following paragraph is currently not true, bug is under
investigation
Regular expression matching is subject to the same limitations that
hold for standard regexen in VCL, for example as set by the runtime
parameters ``pcre_match_limit`` and ``pcre_match_limit_recursion``.
SEE ALSO
========
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment