I am not sure I understand your question, but how does the headers hash
look like? maybe if you show me the result will be easier to understand the
mistake!
Also gives a concrete example of which headers you trying to set.
I have always done curl requests like this:
curl -i --header Accept:
I figured, it's not related to curl but to Rails and Rack only.
Here's what I do:
curl -v -H hello_world: true localhost:3000/empty
Now in the controller I dump the request headers and see
HTTP_HELLO_WORLD=true. Rack converted hello_world to
HTTP_HELLO_WORLD.
But if I try to access the
Hello Roman,
I wrote a blog post about it a while ago:
http://www.andhapp.com/blog/2013/03/03/rack-nginx-custom-http-header-http_-and-_/
I hope it helps.
Anuj
On 23 October 2014 09:39, Roman broilers...@gmail.com wrote:
I figured, it's not related to curl but to Rails and Rack only.
Thanks, Anuj. I didn't know that nginx also makes its contribution to
confusion with headers.
On Thursday, October 23, 2014 11:56:35 AM UTC+3, Anuj Dutta wrote:
Hello Roman,
I wrote a blog post about it a while ago:
4 matches
Mail list logo