Re: Web aficionados - Not allow user to access file directly

Hello Tom, The advantage of the nginx proxy approach is speed and serving multiple domains or sites. For example we have our main site running under the Joomla CMS (no point reinventing the wheel). Nginx proxies requests between joomla and 4D for our 4D Quote system and it is transparent to the

Re: Web aficionados - Not allow user to access file directly

Hi For the HTML markup files, I suggest using the extension .shtml rather than .html For us any direct request for a .shtml file will trigger On Web Authentication and you can catch and reject the request. Doing that allows you to keep things simpler in a single folder and you don't have to

Re: Web aficionados - Not allow user to access file directly

Hi, A few commenters have suggested placing a 4D Web server behind a proxy server. The problem as described can be very easily solved with very little change in complexity and without involving other technologies. One of the reasons we all use 4D is that it allows us to solve problems with

Re: Web aficionados - Not allow user to access file directly

I place nginx as a proxy in front of 4d. Its very straightforward and can run on linux and windows. Nginx runs the public port and can serve all static resources images css etc. You can use lets encrypt for free ssl. This way the proxy to 4D can run on http to say port 8080 which is faster and 4D

Re: Web aficionados - Not allow user to access file directly

Hi Randy, the setup you are looking for is what I have done for all my projects. I have two folders: “WEB_Public” and “WEB_Private”. WEB_Public contains all my static assets like images, javascript, css, etc. There are no 4D tags in any of these files. WEB_Private contains all my application

Re: Web aficionados - Not allow user to access file directly

Randy, On Tue, Oct 1, 2019 at 9:05 AM Randy Engle via 4D_Tech <4d_tech@lists.4d.com> wrote: > Most of our customers are resistant to proxy servers > They think that we should be handling all of it. > Are these the same guys who do such a great job protecting themselves from ransom ware? --

RE: Web aficionados - Not allow user to access file directly

oks via 4D_Tech Sent: Tuesday, October 1, 2019 8:55 AM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: Kirk Brooks Subject: Re: Web aficionados - Not allow user to access file directly Hey Randy, The optimal way to achieve this is to set up the website with a different web server functionin

RE: Web aficionados - Not allow user to access file directly

Hi Lutz, Thanks for the info! Yes, I've got a copy of "Web Companion" somewhere. Will check it out. Randy Engle -Original Message- From: 4D_Tech <4d_tech-boun...@lists.4d.com> On Behalf Of Epperlein, Lutz (agendo) via 4D_Tech Sent: Tuesday, October 1, 2019 8:49 AM To: 4D iNug

Re: Web aficionados - Not allow user to access file directly

Hey Randy, The optimal way to achieve this is to set up the website with a different web server functioning as the node publicly exposed to the internet. That server deals with all the authentication and heavy protection stuff 4D isn't very good at and communicates with your 4D server via API

Re: Web aficionados - Not allow user to access file directly

It's a shame that 4D's web server does not directly support something similar to Apache's .htaccess file in the web root. Securing direct access to html files/folders would then be trivial. Regards, Narinder Chandi, ToolBox Systems Ltd. I am available for new consulting opportunities…