# SoLVED Re: rest-client headers or cookies

**URL:** <https://www.ruby-forum.com/t/solved-re-rest-client-headers-or-cookies/180685>\
**Category:** Ruby\
**Created:** [December 25, 2009, 9:10pm UTC](https://www.ruby-forum.com/t/solved-re-rest-client-headers-or-cookies/180685 "2009-12-25T21:10:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ed\_Howland](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/7993a0/32.png) [@Ed\_Howland](https://www.ruby-forum.com/u/Ed_Howland)\
**Post date:** [December 25, 2009, 9:10pm UTC](https://www.ruby-forum.com/t/solved-re-rest-client-headers-or-cookies/180685/1 "2009-12-25T21:10:28Z")

</div>

The secret sauce for cookies:

resp = RestClient.post(server\_url’ + ‘/resource’, :args =\> “”)  
@session\_cookies = resp.cookies

Then when calling again:  
RestClient.put(’#{server\_url + ‘/resource/id’,  
{:args =\> args}, {:cookies =\> @session\_cookies})

You have to use a payload (:args =\> args) for PUT and it must be the  
first argument. The :cookies hash must be the second argument to  
put().

Cheers,  
Ed

On Mon, Dec 21, 2009 at 5:59 PM, Nicholas W.