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

DelayedJobWeb responds forbidden with Chrome Version 42.0 #78

Open
eiked opened this issue May 16, 2015 · 4 comments
Open

DelayedJobWeb responds forbidden with Chrome Version 42.0 #78

eiked opened this issue May 16, 2015 · 4 comments

Comments

@eiked
Copy link

eiked commented May 16, 2015

routes.rb:
mount DelayedJobWeb => '/admin/tools/delayed_jobs'

This used to work well.

But I now get back a page with status 403 and body: 'Forbidden'
when using Chrome Version 42.0 (it did work with Chrome before)
(fails both in development and production mode)

It still does work as expected when using Firefox v37.0.2

This somehow sounds like they changed something in Chrome that does trigger this bug.
(As it did work before with Chrome and still works with Firefox)

using

  • delayed_job_web (1.2.10)
  • rails 4.2.1
  • ruby 2.2.2p95
@sockmonk
Copy link

sockmonk commented Oct 3, 2015

I started getting Forbidden errors as soon as I upgraded to Firefox 41.0.1. Was working great until then.
delayed_job_web 1.2.10
rails 4.2.4
ruby 2.2.2p95

@mreinsch
Copy link

having same issue; it's actually stranger than this, I'm using chrome with two profiles, and for my main profile I get 'Forbidden', but my developer profile can still access it fine.
I've compared cookies and requests, but couldn't find any obvious issues there.

@hallmatt
Copy link

hallmatt commented Jun 4, 2018

This still seems like an issue with Chrome 67. Works fine with Firefox. Strange! My issue only happens when authenticating the route...

authenticated :user, -> user { user.is_administrator? }  do
    mount DelayedJobWeb, at: "/delayed_job"
  end

Chrome seems to work fine without auth.

@benSlaughter
Copy link

I had this issue, I downloaded and chrome extension to clear my App Cache, Cache, and Cookies. This solved it for me. Best of luck!

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

No branches or pull requests

5 participants