Hacker News new | past | comments | ask | show | jobs | submit login

Are you maybe hitting a cached page on production that can get handled without rails being involved?



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">--- !ruby/object:ActionController::Base bar: 1</id>' --insecure https:localhost




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: