Horizon: Retrying a failed job 419 response

Created on 1 Sep 2017 · 6Comments · Source: laravel/horizon

I have found that I can eventually retry all failed jobs after multiple page refreshes. However, I noticed that some retry attempts do not actually succeed after clicking the retry button. When I pulled up the web inspector, I found that these requests had a 419 unknown status response from the server with a response containing.

{
    "message": ""
}

I don't know the reason for this error (nginx, php 7.1, ubuntu 16.04), but some error handling on the retry button's axios request would at least allow a user to reattempt another retry if a 419 occurs without a full page refresh.

Source

wells

Most helpful comment

I know this is a closed and relatively old topic. But for me the solution was to disable the csrf token validation for the route horizon/* because I have the VerifyCsrfToken middleware in my web middleware group. A solution could be to define a different middleware group and set it in your config: horizon.middleware. Another solution is to skip csrf validation for the horizon/* routes:

VerifyCsrfToken.php

class VerifyCsrfToken extends Middleware
{
    /**
     * The URIs that should be excluded from CSRF verification.
     *
     * @var array
     */
    protected $except = [
        'horizon/*'
    ];

    // ... the rest
}

kaphert on 5 Mar 2018

❤5

All 6 comments

Here's a gif too.

419 Oh my

wells on 1 Sep 2017

I get the same 419 status message when I attempt to monitor a tag as well.

wells on 1 Sep 2017

Can't replicate, retrying failed jobs as well as monitoring tags works fine for me.

themsaid on 4 Sep 2017

VerifyCsrfToken.php

class VerifyCsrfToken extends Middleware
{
    /**
     * The URIs that should be excluded from CSRF verification.
     *
     * @var array
     */
    protected $except = [
        'horizon/*'
    ];

    // ... the rest
}

kaphert on 5 Mar 2018

❤5

I cause the same conflict and if I omit the csrf the same thing happens with the middleware of auth, I think it is a header in the configuration of nginx but not solution solution

mromero91 on 21 Apr 2018

This has been solved in Nova (https://github.com/laravel/nova-issues/issues/323) by adding default headers to Axios based on this piece of code document.head.querySelector('meta[name="csrf-token"]').content. I think it should be added here too. I'm having the issue as well after setting $addHttpCookie = false in VerifyCsrfToken.

This is also part of the Laravel bootstrap JS: https://github.com/laravel/laravel/blob/master/resources/js/bootstrap.js