You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugwash: phk is for not adding -a processing for VEXTs. He suggests a varnish.cf file which would allow for per-extension acceptors (which I appreciate!) and we would probably also need some -Eext.so,-a=...,-a=... or similar.
I still think that using -E to load extensions and then use a consistent -a and -s across all implementations is cleaner and would still prefer that.
Working on a continuation of #3976 the question arose which command line syntax we want for pluggable acceptors. I see two basic options:
-a
here, kind would be the acceptor kind, so a valid use case would be
-a foo=tcp,127.0.0.1:4444
-A
, where kind is mandatoryI like to avoid adding new options, but the first option comes with some ambiguity:
could mean
or
and, because of backwards compatibility, the error message might be confusing:
This can be tried out here: nigoroll@8fcb921
The text was updated successfully, but these errors were encountered: