Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sidekiq 3.4.2 produces Rack::Protection::AuthenticityToken Error when mounting in Padrino #2461

Closed
hbrysiewicz opened this issue Jul 28, 2015 · 3 comments · Fixed by #2462
Closed

Comments

@hbrysiewicz
Copy link

Example Repository

When trying to mount Sidekiq application within Padrino, Rack::Protection::AuthenticityToken Error is produced. See example repository for bare bones demonstration. The exact same project works when Sidekiq is explicitly set to 3.4.1.

Much thanks to the Padrino team and also @jc00ke on the Sidekiq team for the great communication up until now.

@mperham
Copy link
Collaborator

mperham commented Jul 28, 2015

Sorry you are seeing this pain. Sidekiq 3.4.2 requires a session store to fix a severe security issue.

This behavior is not a bug and I'm not an expert in Padrino so I can't tell you how to add a session store. You'll need to consult the Rack / Padrino docs for details. A bare Rack example is here:

https://github.com/mperham/sidekiq/wiki/Monitoring#standalone

@mperham mperham closed this as completed Jul 28, 2015
@hbrysiewicz
Copy link
Author

Hi @mperham I actually did consult the Padrino team before bringing this back to the Sidekiq team. padrino/padrino-framework#1944 who seem to think it is a Sidekiq issue. The standalone doc you have referenced does not actually fix the issue. I realize both teams want to blame the other but would you mind just looking at the example repo or maybe talking to the Padrino team about where the issue lies?

@jc00ke
Copy link
Contributor

jc00ke commented Jul 28, 2015

I believe #2462 should fix this issue. Fingers crossed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants