From the beginning we use OMADA v3.0.5 with an EAP115 operating in a Portal Server environment. Our main goal is to gather several info from the client in the authentication phase via the surface given by our external Portal Server. There are several forms to fill next to each, the forms are posted with an asynchronous xmlHttpRequest request, similar like this:

var xhttp= new XMLHttpRequest();
xhttp.onreadystatechange = function() {
...
}
xhttp.open("POST", "main", true);
xhttp.setRequestHeader("Content-type", "application/x-www-form-urlencoded");
xhttp.send('...data...');
 

The portal worked fine without any issues. Now we have to change the EAP to an outdoor version, so we replaced the EAP115 with EAP110. Normally the two device should be compatible an identical to use. But we experienced a strange issue with the new EAP: everything works well like formerly, but sometimes (often) the post request fails - when the client clicks the send button on the form nothing happens, our webservice does not receive the request. To find the problem we put some debug line into the js source code. Normally the onreadystatechange function is called four times per posts (with readyState 1,2,3,4 - in the last event with readyState=4 + status=200 on success). But when the post fails we can see that the readyState goes only to 1, which means, that the Open() method has been called. State 2,3 never occurs and about 70 secs later the readyState changes to 4 with a status=0, which means: the request failed. We have no idea what is happening in the backgorund.

We tried both changing to the latest OMADA version (v3.2.1) and also to update the firmware of the EAP110 to newest one (3.3.0 Build 20190301 Rel. 37118), but the issue was not solved. Any idea?