Commit 403c75e8 authored by Nils Goroll's avatar Nils Goroll

Bring back STRING + DURATION

This is an (intentional) regression from 6f9595e6,
but I don't see why we should prevent stringifications of DURATION.

Related to #2101 #2102
parent 3bd4f516
......@@ -141,6 +141,9 @@ varnish v1 -vcl {
else if (4) { }
else { }
}
sub vcl_backend_response {
set beresp.http.buzz = "ttl=" + beresp.ttl;
}
}
# XXX: not the most clear error message
......@@ -214,13 +217,6 @@ varnish v1 -errvcl {DURATION + STRING not possible.} {
}
}
varnish v1 -errvcl {STRING + DURATION not possible.} {
backend b { .host = "127.0.0.1"; }
sub vcl_recv {
set req.http.foo = "foo" + 1s;
}
}
varnish v1 -errvcl {DURATION + INT not possible.} {
backend b { .host = "127.0.0.1"; }
sub vcl_recv {
......
......@@ -1027,7 +1027,6 @@ static const struct adds {
{ '+', DURATION, REAL, VOID },
{ '+', DURATION, TIME, VOID },
{ '+', DURATION, STRING, VOID },
{ '+', STRING, DURATION, VOID },
{ EOI, VOID, VOID, VOID }
};
......
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