Thanks for your commentj_McCaffrey. What fixed it was switching from HTTP1.0 to HTTP1.1, adding the host header and changing the uri.
The logs didn't tell us anything, and the params were ok. The problem was not fully grasping the HTTP header requirements. Thanks again. Dana On Monday, August 17, 2015 at 3:37:30 PM UTC-6, Dana Baillie wrote: > > Hi we have a Ruby on Rails server application on Heroku. When I send a > post request to it, I always get a 400 Bad Request response. I have > searched other 400 errors, but none are related to our issue. The HTTP > response that we receive looks like this below: > > HTTP/1.1 400 Bad Request > > Server: Cowboy > > Date: Fri, 14 Aug 2015 21:55:25 GMT > > Content-Length: 0 > > The post request that I am sending looks like this below: > > POST http://ourapp.herokuapp.com/api/v1/requests HTTP/1.0 > > Accept-Language: en-us > > Accept: text/plain > > Content-Type: application/x-www-form-urlencoded > > Content-Length: 38 > > Connection: Close > > request=600&key=&newKey=danasecretkey& > > If I create an HTML form to send the data, there is no issue. It's when I > try to send the same request from our file server, that I get the errors. I > tried using a preflight request with all of the correct request headings, > but received the same 400 Bad Request error. It's the same whether I use > HTTP or HTTPS. > > > Does anyone have any suggestions as to what I might be doing wrong? > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
