As the asynch nature of it may trigger events in another order. A c-ares
upgrade made it break.
Reported-by: Marc Hörsken
Fixes #6247
<server>
http
</server>
-# don't run this with the threaded-resolver since the events might trigger in
-# a different order!
+# don't run this with the threaded-resolver or c-ares since the events might
+# trigger in a different order!
<features>
!threaded-resolver
+!c-ares
</features>
<name>
HTTP with shared cookie list (and dns cache)