I've recently moved a 3.0 app ta 3.1 and am finding that
ActiveResource breaks after a successful post because we now check for
the presence of the Content-Length header after a successful create
(basically whenever the API returns a 201). The API is also on 3.1,
and this only happens on staging/pre-prod/prod.
I'm still investigating, but one thing that is clear is that the API
response doesn't have a Content-Length header and this causes
AResource to break; the fact that this only happens on the prod server
seems to point at the fault probably lying with Apache.
Has anyone run into a similar issue?