Cuong Manh Le
Cuong Manh Le
> Ah... I think this is something that the Go `net/http` stdlib helpfully "fixes" for us 🤦♂ The good news is that it seems circumvent-able: https://stackoverflow.com/questions/24945806/add-unaltered-lowercase-headers-to-golang-http-request > > Thanks for...
See: https://github.com/golang/go/issues/52372
cc @kardianos
We do have `minIterationDuration` which will be disable when set to 0.
> Don't some operating systems (depending on security policy) throw a confirmation dialog when attempting to listen on any interface other than the loopback? I don't know about this, I...
> > Don't some operating systems (depending on security policy) throw a confirmation dialog when attempting to listen on any interface other than the loopback? > > > > Yes,...
> I think the real problem is that `SupportsIPv6` isn't defined well enough. > > > > It says: > > > > > SupportsIPv6 reports whether the platform supports...
> For me, I'm leaning to report that we can do IPv6 at least on one of all interfaces. That also help us implementing more easily using RoutedInterface. Something like...
I mailed https://go-review.googlesource.com/c/net/+/460735 for fixing the tests. The problem is not about `RoutedInterface`, but the code path that rely on old (wrong) behavior needs to be updated.
This is introduced in https://go-review.googlesource.com/c/go/+/392834, and Unified IR also has this problem until https://go-review.googlesource.com/c/go/+/421821. ~We need to ensure non-Name call in subexpression call is also rewritten.~