Too frequent ajax session failures

Too frequent ajax session invalidation laravel5apacheSession is stored in Laravelfile in the code, and the polling speed is too fast. For example, 30 ajax requests will cause the Session to become invalid. After Google finds a similar problem in the same industry outside of China, I did not find the answer. There are other solutions, no...Too frequent ajax session failures

• Laravel 5

• Apache

SessionStored inLaravel file

In the code, the polling speed is too fast, such30 times/second ajaxRequest will causeSessionInvalid

Google found similar problems in the same industry abroad, but I did not find the answer.

There are other solutions that do not exist infile, ExistsredisCan solve this problem, I guess it isIOCause ~

Have you ever encountered a similar situation?

Description

The first time I encountered this problem, I thought it was a version problem.5.0Upgrade5.1.

It is a simple re-occurrence. The page has a page, which is usedajaxTo retrieve data, I started to click the page number, but waited for ajax to return. I continued to click the next page number.401.

ThesessionOnly login users can obtain data, but the data retrieval logic does not have anysessionOperation

Github

Someone reported this bug.
Bug

Reply content:Too frequent ajax session failures

• Laravel 5

• Apache

SessionStored inLaravel file

In the code, the polling speed is too fast, such30 times/second ajaxRequest will causeSessionInvalid

Google found similar problems in the same industry abroad, but I did not find the answer.

There are other solutions that do not exist infile, ExistsredisCan solve this problem, I guess it isIOCause ~

Have you ever encountered a similar situation?

Description

The first time I encountered this problem, I thought it was a version problem.5.0Upgrade5.1.

It is a simple re-occurrence. The page has a page, which is usedajaxTo retrieve data, I started to click the page number, but waited for ajax to return. I continued to click the next page number.401.

ThesessionOnly login users can obtain data, but the data retrieval logic does not have anysessionOperation

Github

Someone reported this bug.
Bug

I agree with @ lialosiu's answer. Generally, this is the case where the file is locked or cannot be read due to high concurrency, so the session becomes invalid. You can use mencache to save the session.

Laravel 5.1.27 LTS indicates the middle trick. It should be a problem of processing session file in high concurrency... it can be solved without file.

Can I provide a description link for a foreigner to solve this problem?