Way to pass CSRF token on authenticate?

[nickelser]

Right now I have to use a slightly modified version of pusher.js instead of the hosted one, as right now pusher does not set "X-CSRF-Token" which is required by my rails app. I'm not entirely sure what the best way to do this on a global level would be, but I added a line like this to make it work:

xhr.setRequestHeader("X-CSRF-Token", Pusher.csrf_token)

(and set Pusher.csrf_token = $('meta[name="csrf-token"]').attr('content') before calling pusher init).

[borski]

I have this same issue. nickelser: Can you be more specific as to how you got around this?

[nickelser]

make sure you are including the csrf_meta_tags helper in your view, run the Pusher.csrf_token = $... code in some global init block, and then run setrequestheader in the ajaxsetup call.

in coffeescript, I have a function like this:

init_csrf = ->
  window._settings.token = $('meta[name="csrf-token"]').attr 'content'

  $.ajaxSetup
    beforeSend: (xhr) ->
      xhr.setRequestHeader "X-CSRF-Token", _settings.token

[ThisIsMissEm]

This isn't actually yet done, I'm working on a patch this week which should be released in the next couple of weeks.

[brumm]

I'm having this problem as well, and it's been a while - Any progress on this?

[leggetter]

It's possible to pass additional parameters to be passed along with channel_name and socket_id by passing additional options to the Pusher constructor. This provides a way of defining additional query parameters and headers.

You can read the documentation here:
http://pusher.com/docs/client_api_guide/client_connect#options_parameter