Verizon transparent web caching issue? WASRe: Data Center QoS equipment breaking http 1.1?

Disregard my disregard. The problem resurfaced with no changes on my part. I purged browser caches and tried them from 3 browsers and each time: http://www.countytheater.org redirected to: http://webmail.ns3.pil.net/ which is another NameVhost on that server sharing that IP. This is inc

Re: Verizon transparent web caching issue? WASRe: Data Center QoS equipment breaking http 1.1?

Quoting u...@3.am: Disregard my disregard. The problem resurfaced with no changes on my part. I purged browser caches and tried them from 3 browsers and each time: http://www.countytheater.org redirected to: http://webmail.ns3.pil.net/ which is another NameVhost on that server sharing that

Re: Verizon transparent web caching issue? WASRe: Data Center QoS equipment breaking http 1.1?

Again, turned out to be my own stupidity. It was just DNS on a secondary DNS server, which was pointing to the old IP, which was redirecting to the new IP, but at that point, the headers are lost. I would have thought that on MacOSX (my client; the server is FreeBSD 7.2-STABLE), if I tell t

Re: Verizon transparent web caching issue? WASRe: Data Center QoS equipment breaking http 1.1?

On 1/08/2009, at 1:06 PM, u...@3.am wrote: Again, turned out to be my own stupidity. It was just DNS on a secondary DNS server, which was pointing to the old IP, which was redirecting to the new IP, but at that point, the headers are lost. I would have thought that on MacOSX (my client;