Re: Restricting to one folder hierarchy on the entire server
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 61778
interpreted = N
texte = You could also turn on WebDNA for only the virtual host if that is mapped to the directory for your client. Usually each site is stored in a different directory. By default Apache will serve the page uninterpreted if WebDNA is not processing the page, but this is the right result. WebDNA will not be passed the page if Apache does not pass to the cgi, so it as if the page were a normal text. You could ban access to .tpl in other directories. Look at how WebDNA blocks .db access in its httpd.conf instructions. You could map the .tpl to an error page in other directories, but why do that? Just keep the .tpl files out of the other directories. Bill-----Original Message-----From: Kenneth Grome
Sent: Fri, 15 Apr 2005 12:22:01 +0800To: "WebDNA Talk" Subject: Restricting to one folder hierarchy on the entire server ...I have a client who wants to use WebDNA on the server, but the server admin guy wants to insure that WebDNA never serves .tpl pages from any other directory or domain on the server. In other words, he wants to make sure that the only .tpl pages that are ever served by WebDNA are the .tpl files in my client's folder hierarchy.Is this possible?My first thought was that the server admin guy might be able to configure a single sandbox for this user -- and that will be the only sandbox on the server. Then only the .tpl files in his domain will be served by WebDNA, and any other .tpl files on the server will be ignored.But they wouldn't really be ignored, would they? So now I'm wondering what will happen when a request is received for .tpl pages that reside in a different folder hierarchy on the server?1- Will Apache serves those pages directly, or ...2- Will WebDNA serve them WITHOUT interpreting the webdna tags in those pages, or ...3- Will WebDNA serve them after interpreting the webdna tags in those pages, or ...4- Will WebDNA generate and serve an error message after receiving the request for these "unauthorized" .tpl pages?Sincerely,Kenneth Gromewww.kengrome.com-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
You could also turn on WebDNA for only the virtual host if that is mapped to the directory for your client. Usually each site is stored in a different directory. By default Apache will serve the page uninterpreted if WebDNA is not processing the page, but this is the right result. WebDNA will not be passed the page if Apache does not pass to the cgi, so it as if the page were a normal text. You could ban access to .tpl in other directories. Look at how WebDNA blocks .db access in its httpd.conf instructions. You could map the .tpl to an error page in other directories, but why do that? Just keep the .tpl files out of the other directories. Bill-----Original Message-----From: Kenneth Grome Sent: Fri, 15 Apr 2005 12:22:01 +0800To: "WebDNA Talk" Subject: Restricting to one folder hierarchy on the entire server ...I have a client who wants to use WebDNA on the server, but the server admin guy wants to insure that WebDNA never serves .tpl pages from any other directory or domain on the server. In other words, he wants to make sure that the only .tpl pages that are ever served by WebDNA are the .tpl files in my client's folder hierarchy.Is this possible?My first thought was that the server admin guy might be able to configure a single sandbox for this user -- and that will be the only sandbox on the server. Then only the .tpl files in his domain will be served by WebDNA, and any other .tpl files on the server will be ignored.But they wouldn't really be ignored, would they? So now I'm wondering what will happen when a request is received for .tpl pages that reside in a different folder hierarchy on the server?1- Will Apache serves those pages directly, or ...2- Will WebDNA serve them WITHOUT interpreting the webdna tags in those pages, or ...3- Will WebDNA serve them after interpreting the webdna tags in those pages, or ...4- Will WebDNA generate and serve an error message after receiving the request for these "unauthorized" .tpl pages?Sincerely,Kenneth Gromewww.kengrome.com-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
devaulw@onebox.com
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
I've been thinking (2002)
[OT] Bad Hard Drive? (2003)
Cart Numbers (1997)
Nested tags count question (1997)
Lock out multiple users with same password? (1999)
[WebDNA] Google map mashups (2010)
Looping control (1997)
[WebDNA] Upgrade from OS 10.7.5 WebDNA 6.2 to Mavericks (2014)
Re2: frames & carts (1997)
[ShowNext] feature in 2.0 (1997)
Aaron kant add (or whatever it was) (2000)
[AppendFile] problem (WebCat2b13 Mac .acgi) (1997)
emailer (1997)
Security (1998)
syntax question, not in online refernce (1997)
More on the email templates (1997)
[WebDNA] My SQL will not Connect (2020)
Email template names (1997)
Search context not finding recent entries (1998)
FileMaker and WebCat - .hdr OK Merge not OK (1999)