[master] a0a3dfcff use backend None instead of bad_ip backend

Nils Goroll nils.goroll at uplex.de
Thu Oct 17 13:06:41 UTC 2019

On 14/10/2019 14:46, Dridi Boukelmoune wrote:
>>     This avoids issues with failing tests when bad_ip is actually reachable
>>     via tcp on the respective port, as seen for example with b00068.vtc
> I thought I had taken care of this last time I ran into this problem
> but I suppose only a subset of the test cases failed me for this
> reason. Should we evaluate the remaining uses of ${bad_ip} and
> consider retiring it? Especially since it is purely arbitrary and not
> really "bad" per-se.

I do not think we should try to catch cases caused by "security software" which
some enterprises may or may not use



** * * UPLEX - Nils Goroll Systemoptimierung

Scheffelstraße 32
22301 Hamburg

tel +49 40 28805731
mob +49 170 2723133
fax +49 40 42949753



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-commit/attachments/20191017/5b33eb41/attachment-0001.bin>

More information about the varnish-commit mailing list