On May 26, 12:26 pm, Rick DeNatale <[email protected]> wrote:
> The same thing happens with Safari 4, Firefox, and Curl, so it's not a > browser caching issue. > > I suspect that Apache and Passenger are not sending the request > through, I restarted apache on the server and still the same thing. > > Ideas anyone? Not so much an idea as what I would look at next; have you tried using tcpdump (or wireshark, ethereal, etc) to see what the http requests/ responses look like ? Fred > > -- > Rick DeNatale > > Blog:http://talklikeaduck.denhaven2.com/ > Twitter:http://twitter.com/RickDeNatale > WWR:http://www.workingwithrails.com/person/9021-rick-denatale > LinkedIn:http://www.linkedin.com/in/rickdenatale --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
