How To Persist Cookies

[Kevin Pruett]

I'm struggling with persisting/accessing cookies from different endpoints. I have a Grape API + a Backbone.js front-end. I'm using NGINX to avoid CORS conflicts and proxy-passing API endpoints to http://api.domain.dev and front-end routes to http://domain.dev

Here is how Rack Cookie is setup

use Rack::Session::Cookie, secret: rand.to_s, domain: '.domain.dev'

When I hit a route I can set the cookie, but on subsequent requests, those cookie values are lost.

Can someone help? Many thanks.

[Kevin Pruett]

I should mention that I'm setting the cookie and immediately redirecting like so:

cookies[:gh_user] = {

  name:  auth.info.name,

  email: auth.info.email,

  uid:   auth.uid,

  token: auth.credentials.token

}

redirect "#{ENV['REGISTRATION_REDIRECT']}?message=successful%20authentication" if params['type'] == 'registration'

On the browser end, I see only a rack.session cookie being set. Pinging another route and trying to access the previously set cookie fails.

[Daniel Doubrovkine]

Does anything change if you don't redirect but return a body? Could be a bug where we don't write out cookies on a redirect.

--
You received this message because you are subscribed to the Google Groups "Grape Framework Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ruby-grape+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

dB. | Moscow - Geneva - Seattle - New York
code.dblock.org - @dblockdotorg - artsy.net - github/dblock

[Kevin Pruett]

Unfortunately no, it appears that the session is reset and cookies do not persist. This very well may be a symptom of my setup.  Do you have any examples of how a JS front-end communicates with a Grape API properly passing cookies? I'm using a combination of Rack::Cors and NGINX. Not sure if certain configuration is necessary.

Thanks

[slowjack2k]

Grape Cookie != Rack::Session::Cookie

You'r using a "custom" middleware to encrypt you'r cookie. If you want to use this cookie
you have to access

env["rack.session.unpacked_cookie_data"]

with grape's cookie you access the cookie as plain data.

The next question is where do you use the `use` statement? Use applys to the current namespace and all children
namespaces.

@Daniel, redirect isn't an issue. Within Endpoint#run the cookie is read and written. redirect does not by pass this cycle.

What an issue can be is

Rack::Utils.set_cookie_header! # Line cookies.rb#17

No parameter for Domain, Path, age is set.

@Kevin Try to access your cookie via env["rack.session.unpacked_cookie_data"] or try this issue https://github.com/intridea/grape/issues/715

regards
dieter

[slowjack2k]

PS: It's not obvious but documented.

You have to set:

cookies[:gh_user] = {

 name:  auth.info.name,

 email: auth.info.email,

 uid:   auth.uid,

 token: auth.credentials.token,
 domain: '.domain.dev'

}

If you don't do it you'r cookie from grape is restricted to api.domain.dev

But keep in mind grape cookies are not encrypted or secured.

[Kevin Pruett]

thanks for the reply @slowjack2k

do you recommend using `Rack::Session::Cookie` or `Grape Cookies`?

I'm receiving nil when checking for cookies

env["rack.session.unpacked_cookie_data"]#=>nil

Is the another preferred way of maintaining state? Is there anything else that I could be doing wrong that you know of?

[slowjack2k]

Personally I don't maintain state within cookies at all. I use https://github.com/faber-lotto/grape_api_signature and sign every request.

env["rack.session.unpacked_cookie_data"]

Is only used internaly the request object should have a session accessor.

I would suggest that you wait one or two days and track the named issue above within grape.
Some discussions are going on. Maybe cookies & session will become a seperate gem
https://github.com/faber-lotto/grape_session

[Kevin Pruett]

thanks, these look great. really like the signed signature approach. didn't know about that

--
You received this message because you are subscribed to a topic in the Google Groups "Grape Framework Discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ruby-grape/q8ifOz8rjCs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ruby-grape+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Kevin Pruett
pruett...@gmail.com
http://www.twitter.com/pruett