Many time 401 "Unauthorized." on ajax requests

What are the sources you're pulling the ajax request from? Do you control them?

What happens if you load the ajax url in to your browser? Do you get the same errors?

It is possible that you're being rate limited by the site. The site could be seeing you hit it too many times and not allow it.

There are all kinds of factors here.

What are the sources you're pulling the ajax request from? Do you control them?

• The source is a page view action triggered by some of my javascript code

What happens if you load the ajax url in to your browser? Do you get the same errors?

• No, i can refresh the page I've loaded via ajax an can not reproduce the error.

It is possible that you're being rate limited by the site. The site could be seeing you hit it too many times and not allow it.

• Only if laravel has a protection of that by default. I've not implemented a rate limit into laravel.

I'm having very similar problems. I keep getting 401 responses from ajax calls and I think it is because my auth session variable keeps dying.

I'm having to avoid using the .env file for configuration as the sites read from the wrong (i.e. each other's) .env files.

I'm using Laravel 5.*, PHP 5.5.9, Apache 2, Windows Server 2012.

Do you validate your data ? If so you have to set the authorize method to true in your Requests. For example: app/Http/Requets/Authenticate

    /**
     * Determine if the user is authorized to make this request.
     *
     * @return bool
     */
    public function authorize()
    {
        // set to true instead of false
        return true;
    }

Otherwise you get a "not allowed error". https://mattstauffer.co/blog/laravel-5.0-form-requests http://laravel.com/docs/master/validation#form-request-validation

"If the authorize method returns false, a HTTP response with a 403 status code will automatically be returned and your controller method will not execute.

If you plan to have authorization logic in another part of your application, simply return true from the authorize method:"

This issue is also existing on a Laravel 5.0.* I am currently working on. Does someone have a solution?

When making simultaneous XHR requests, session data may be lost due to concurrent requests updating the session at the same time. This is a known issue. One solution may be reducing the number of requests, or use **session locking **. This allows to lock the session file when used, hence forcing all requests to be executed one after the other. This may slow down your app, but eliminate the potential errors.

Laravel does not include session locking by default. Someone made a Laravel package to add the feature. https://github.com/rairlie/laravel-locking-session

It seems to have worked for me.

This is due to your login session. Whenever your session expire. Request Response is "Unauthorized".

I also have the same problem on 5.2, which I think is the result of making multiple simultaneous AJAX requests, some of which were to the same URL, which makes no sense I know.

Anyway, the session locking package suggested by chijipon works as a temporary solution for me. I no longer lose my sessions.

maybe this comment help someone there:

my case was the localhost part in the url, I have one page loaded with a vue component that have the vue-resource this.$http.get('api/....') with the proper CSRF headers, called on the component mount()/ready().

Laravel served on the port 3000, the issue was that the localhost:3000 on the url was translated to the IPV6 [::1]:3000 and here was the weird behaviour, sometimes it's worked and the data was loaded successfully, sometimes it's 401 unauthorized.

moving to a custom domain defined on the hosts file pointing to 127.0.0.1 = custom.domain:3000 solved the issue for me.

In my case http://127.0.0.1:8000 throws the exception, using http: // localhost: 8000 solve.