This could be a cache problem, so you might try using a post instead of a get. I've run into a similar issue in the past, and it had to do with the browser (IE in my case) not making the call because it had a response to that request in its cache.
Its my understanding that you can also fix it by sending the proper headers with the response, but I didn't try that since what I was doing didn't really need to be a get. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
