We had the same issues. As Jörg Hoh mentioned, this is coming from the Publisher, not the Dispatcher. The strange part to us was that it behaved differently when hitting the Publisher directly vs through the Dispatcher (via IP) vs through a LB (via DNS). I'm not quite sure why this was yet.Both of these requests are from the access.log on the Publisher (and both going through the Dispatcher, one via direct IP to the Dispatcher one via DNS to a LB in front of the Dispatcher)172.99.99.10 - anonymo...