I think it should be OK. It uses ink_inet_port_cast which extracts the port without changing byte order. TSNetConnect used ink_inet_get_port which flips the byte order. I think I will add it to the patch to not bother to extract the address and port (that was needed before the changes in 3.1.0).
Tuesday, August 23, 2011, 4:57:05 PM, you wrote: > After looking at 3.1.0, is it possible that TSFetchUrl might also have > the same problem?
