(Sorry, sent this earlier but “from” the wrong email address so the list didn’t pick it up.)
A few things to consider: 1) Even if you’re only serving dynamic pages, you can configure a front-end server to directly serve images and Javascript files, letting everything else proxy through to 4D. That will offload a lot of “static” processing from your database. 2) If you’re supporting multiple domains, having a front-end will let you serve virtual domains, each with its own TLS certificate. Then you can just proxypass to the port the database is listening to (excluding .js, .jpg, and other static files). 3) The Mac (and, I believe, Windows) both require workarounds to have 4D listen to port 80, such as having the database run as root. Using Apache or IIS as a front-end with a proxy, the database can listen to a higher-range port. I hope this is helpful! Ron Rosell __ Ron Rosell President StreamLMS 301-3537 Oak Street Vancouver, BC V6H 2M1 Canada Direct phone (all numbers reach me) Vancouver: (+1) (604) 628-1933 | Seattle: (+1) (425) 956-3570 | Palm Beach: (+1) (561) 351-6210 email: [email protected] <mailto:[email protected]> | fax: (+1) (815) 301-9058 | Skype: ronrosell > On Nov 25, 2019, at 1:19 PM, Richard Wright via 4D_Tech > <[email protected]> wrote: > > I’m only interested in serving through On Web Connection, no static pages. So > why do I need anything in front of 4D? Are there known vulnerabilities in 4D > other than bad programming? Is there anyway to “break” into the data? Or > “break” into files that don’t exist in the web folder? What does putting > something in front of 4D gain? ********************************************************************** 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] **********************************************************************
