On Jul 11, 2006, at 19:15 , David D. Kilzer wrote:
It seems a bit odd that the same cookie is set four times.
Yeah, it's one of the things that needs cleaning up, but I don't think that's causing the problem.
What's the "X-Actual-Host" header for?
X-Actual-Host is used in debugging problems. It lets us know which server actually fielded the request when hitting the load balancer.
What did the original request headers from Safari look like? Have you used a packet sniffer like Ethereal or tcpdump to find out what the traffic looks like between your development server and Safari? Have you compared them to traffic to your production server?
I tried to use tcpdump to see this, but got useless results. Clearly I don't know how to call it. sudo tcpdump -i lo0 -qA didn't really work for me. I got mostly periods, and what little recognizable text did appear didn't seem to be complete (in this case I'm running the server and Safari on the same machine).
Do you have proper DNS entries set up (both forward and reverse) for your internal server on your internal network?
Fairly sure, but it's not clear to me why this would make a difference. Other browsers/feed readers seem to have no problem. Thanks! -- Rick