Yes, for a certain class of errors, 4D sends a HTTP 500 error response and a HTML body with the error information. You should try your test locally to verify.
Of course, you should have a error handler and be able to capture any error and log it if you are using the HTTP server. Unfortunately, there are several types of pointer errors that 4D's error handler won't capture even if you have an error handler. Instead 4D shows a dialog with "Continue" and "Abort" buttons on the web server or to the end user if not a web process. I'm not sure which is worse. But with the web server, the process is stuck until someone comes along and presses the button. John DeSoi, Ph.D. > On Sep 20, 2019, at 3:18 PM, Narinder Chandi via 4D_Tech > <[email protected]> wrote: > > Possibly the error is returned to the client making the request but in my > case it's an external service making the request and I can't see the response > the service receives other than the fact it appears to fail. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
