WHM / Apache Server Configuration + jQuery Ajax

3

Recently I started having the following problem in the domains of my server with WHM:

When running an asynchronous AJAX call in the background, I can not continue, that is, I can not access anything in the same domain by the same terminal that ran the call while the process does not complete.

This gives the impression of slowness in the system, when in fact it is only the problem of the domain being "locked" while there is a process in the background (even if you open another browser tab)

If you access from another terminal - even if it is on the same network - it accesses normally.

This is something that happens in local tests (using PHP Built in) because BuiltIn does not allow more than one simultaneous connection.

But this should not happen on the server.

As it was not like this before, I believe this is due to some change in the server settings.

But as I have no idea what it might be, I can not find anything in the settings that might cause this behavior.

Obs: The system is made in PHP 7. The server uses apache 2.4 + CloudLinux to avoid abuse of resources by a single domain

    
asked by anonymous 25.08.2017 / 19:55

2 answers

2

Problem solved

A while ago, I had a similar problem reported here: Running processes in the background - Accessing same script twice

However, this time the reason was different: the last update of our server with WHM changed a policy that prevented Cross-Domain. And since many of our processes use CORS, there was a deadlock.

To fix, instead of changing the server to work, we made use of the hint in this other link: #

Ajax-cross-domain-with-javascript-pure-

I hope the tips in these 2 links can be of help to others who have similar problems.

Thanks in particular to @WendelRodrigues for the help provided!

    
31.08.2017 / 15:33
0

Maybe this link might help you: Apache / PHP server does not respond while you are making a SOAP request It seems to be a similar problem to what you described, so when you access from another terminal it works, because the lock may be in your session.

    
31.08.2017 / 14:52