This is an odd one, so please bear with me...
I think we're all aware of the trials of getting Rails to play nicely under 10.7.x.
My working set-up was 10.7.3, Rails 3.x, using Passenger, and virtual hosts under Lion's variant of Apache.
This was all working great (testing heavily), until I recently upgraded to 10.7.4...
Initially, all seemed fine, until I found that one particular access (a HTTP POST) consistently returned HTTP Response code 404 when accessing the Rails app from an iPhone app using JSON. Other GET and POST accesses work fine, but just this URL POST returns 404 - regardless of Body data (i.e. the record I'm trying to create). Strangely, the Rails app continues to work fine for the equivalent POST when accessed via a web browser.
I've investigated this, and I've found that, stopping and starting the web server, I can eventually get the access from the iPhone app to complete normally (although, oddly, a reboot alone won't fix it).
Specifically, I can get it to work again via some combination of stopping the web server via the Lion Server admin utility, and then entering 'apache stop' at the command line. Then, after a wait, I then restart the web server via the Lion Server utility (which automatically restarts the stack via Passenger). This technique does not always work (far from it) but after a few tries, I normally get to the point where the access from the iPhone app works again. Once it's working, it stays working until I next stop the web server.
The fact that I can complete the POST via a browser, but not the iPhone app seems to imply the Rails app has restarted OK, and that the routing is OK (at least for HTML). Other JSON accesses are working.
I know this is a long shot, but I thought I'd post it here to see if anyone else is seeing similar problems?
I'm certain this problem has only appeared since I upgraded to 10.7.4.
Any thoughts or similar experiences with Rails and 10.7.4 welcome.