I'm just now getting back to this and have discovered something but am stumped about the solution.
This is running Active4D 5.0 (latest) 4D Remote (client) v11.8 NTK Web Server configured to only accept requests from local hosts. Apache 2 is in front of 4D. The problem was/is that some Active4D error pages are serving as type text/plain. The html text response displays in the browser. Through trial and error I discovered that if make a localhost:8080 call on the web server machine to a page that would give that error, the expected Active4D error response serves fine. That request is bypasssing Apache. So this isn't an Active4D problem. It is either an Apache config issue or something with my rewrite rules. Our old system was running Apache 1. My rewrite rules haven't changed. Would anyone have any idea where to look in Apache configs to find what might be causing an Active4D error response to be passed through and served by Apache as text/plain? Thanks, Brad On 9/21/10 3:31 PM, Brad Perkins wrote: > On 9/21/10 9:51 AM, Aparajita Fishman wrote: >>> That setting is left blank >> Then I'm stumped, I can't reproduce it. >> > Can I expect creating a custom error page to solve this? > > I only ask because I've always used the default, have other > priorities, and don't want to figure out how to create a custom page > if it isn't likely to solve the problem. > > Thanks, > > Brad > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev > Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/ > _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
