Mike Lothian

We're moving to use a file, just need you to confirm what passing /dev/null was equivalent to, then I'm happy to close this

It looks like these two tests are failing: 2023-07-13T18:53:37.6960895Z FAIL: tests/testHttpRequest 2023-07-13T18:53:37.6960984Z FAIL: tests/testIpAddress

``` =================================================== Squid Web Proxy 7.0.0-VCS: src/test-suite.log =================================================== # TOTAL: 34 # PASS: 32 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .....

@rousskov I'm not 100% sure what these tests are trying to do, I've manually tested this change using curl: IPv6 enbled proxy host curl -v -k -x proxyhost:8080 https://google.com curl...

I'll be putting 6.1 with this patch into production (the only place we saw the segfaults) next week some time

I think I'm understanding what the issue is.... http://2000:800::45/foo is being tested, and it isn't being detected at IPv6 ``` + else { + /* + * NP: =(sockaddr_*) may...

I'll rebuilt 6.1 tomorrow and redeploy to our test proxies. I should be able to schedule production for Thursday & Friday

I've been running this patch in production since Thursday (again't 6.1 without the test changes) and there have been no issuess

> > I've been running this patch in production since Thursday (again't 6.1 without the test changes) and there have been no issuess > > @FireBurn, thank you for testing...

Hey, are we any closer to getting this bug fixed? And by that I mean squid segfaulting