revacuate

4 ms·

1. 1.▲
   by revacuate 14y ago

   This is what I had done: 1. Edit Gemfile and change rails version from 2.3.14 to 2.3.15. 2. Commit and push changes 3. bundle exec cap deploy (this is our standard method and works well.) 4. Double check rails -v returns 2.3.15 on productio
2. 2.▲
   by revacuate 14y ago

   Thank you, it turns out I was able to get the curl command to run against production site by adding the --insecure option and using the default port: curl -i -H "Content-Type: application/xml" -X POST -d '<id type="yaml">--- !
3. 3.▲
   by revacuate 14y ago

   Using the above curl command I was able to verify that an old rails 1.2.3 app that I pretend-maintain for a friend returned the ID as a string. Since it is a string and not an object, it's safe. That's all I know. From what I gather/conject
4. 4.▲
   by revacuate 14y ago

   Are you running this test against your development or production site? I can't get it to run against my production site, (nothing appears in the log at all,) but I have triple checked everything and am still getting the same unwanted result
5. 5.▲
   by revacuate 14y ago

   I just updated our app from 2.3.14 to 2.3.15, yet when I run your curl command I'm getting: Parameters: {"id"=>#<ActionController::Base:0xb570d2e8 @bar=1>} Why do you think I'm still unprotected after updating to the fi