There seems to be a problem with the AjaxCallback mechanism when FastCGI is in use?
In practice what we saw was, when logged into the POS lane as cashier, entering "anything" into the main input box, it was ignored and nothing would happen. The front-end was submitting entry to the web server, but the response was totally empty.
Finally figured out that the server wasn't able to determine the SCRIPT_FILENAME value using current code. After some searching I found this which mentioned FastCGI, and then I confirmed that we are using FastCGI for the install where this bug was seen.
So this commit "fixes" for the install in question, but I'm not sure what the implications are of merging it..? Seems safe enough to me but you may have better ideas.
There seems to be a problem with the
AjaxCallbackmechanism when FastCGI is in use?In practice what we saw was, when logged into the POS lane as cashier, entering "anything" into the main input box, it was ignored and nothing would happen. The front-end was submitting entry to the web server, but the response was totally empty.
Finally figured out that the server wasn't able to determine the
SCRIPT_FILENAMEvalue using current code. After some searching I found this which mentioned FastCGI, and then I confirmed that we are using FastCGI for the install where this bug was seen.So this commit "fixes" for the install in question, but I'm not sure what the implications are of merging it..? Seems safe enough to me but you may have better ideas.