Web*3 virtual hosting Webcatalog problem
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 16990
interpreted = N
texte = I was testing Web*3 with Webcat 2.1 and 2.1.1, and came across a potential problem.With a virtual host of www2.tfaw.com and a server name of www2.dhorse.com, the root folder of the tfaw domain is /-tfaw, which I defined in the Web* Virtual Hosts plugin.The problem is that not only do html pages assume this new root, but Webcat now uses this root directory as well. So if I have a database located at /DB/file1.db, then [LOOKUP db=/-tfaw/db/Holding.db&...] is accessible from the dhorse domain, but not from the tfaw domain. The error message is Database /-tfaw/db/Holding.db not found with the virtual root being /-tfaw/, thus causing an extra /-tfaw/ in the path).This behavior differs from previous version of Web* used in combination with a VDM plugin such as Firesite, where all webcat file references were relative to the main Webstar root. Firesite also cleans the redundant directory names as an added bonus.So my questions are:1) Is the intended Webcat behavior to use virtual root folders for FILE references defined by the Web* Virtual Hosts plugin?2) If so, why does it behave differently with Firesite 2.3d4 and Web* 3 (Webcat uses a single root folder, /)?3) Using the Web*VH plugin, I am assuming that sharing databases, files, and the Webcatalog folder between virtual hosts may only be achieved by nesting folders or by using aliases. Is this correct, or am I missing something?4) What is the current data on how much overhead is caused by using aliases to either files or folders in Webcat and Webstar?I'm not terribly excited about rearranging all our databases (and references to them!) into a 3-level nested configuration to allow database sharing between all our sites and ssl, so I think I would be stuck with aliases in this case.Unless I just stick with Firesite where everything works as it did before, as soon as the dev version stabilizes a bit and stops spewing 200mb debug logs.Comments anyone?Thanks,Dale ________________________ ______________________________ | Dale LaFountain | mailto:dalel@dhorse.com | | MIS Director,WebMaster | web: http://www.dhorse.com/ | | Dark Horse Comics, Inc.|Phone: 503-652-8815 x324 | \________________________|______________________________/
Associated Messages, from the most recent to the oldest:
I was testing Web*3 with Webcat 2.1 and 2.1.1, and came across a potential problem.With a virtual host of www2.tfaw.com and a server name of www2.dhorse.com, the root folder of the tfaw domain is /-tfaw, which I defined in the Web* Virtual Hosts plugin.The problem is that not only do html pages assume this new root, but Webcat now uses this root directory as well. So if I have a database located at /DB/file1.db, then [LOOKUP db=/-tfaw/db/Holding.db&...] is accessible from the dhorse domain, but not from the tfaw domain. The error message is Database /-tfaw/db/Holding.db not found with the virtual root being /-tfaw/, thus causing an extra /-tfaw/ in the path).This behavior differs from previous version of Web* used in combination with a VDM plugin such as Firesite, where all webcat file references were relative to the main Webstar root. Firesite also cleans the redundant directory names as an added bonus.So my questions are:1) Is the intended Webcat behavior to use virtual root folders for FILE references defined by the Web* Virtual Hosts plugin?2) If so, why does it behave differently with Firesite 2.3d4 and Web* 3 (Webcat uses a single root folder, /)?3) Using the Web*VH plugin, I am assuming that sharing databases, files, and the Webcatalog folder between virtual hosts may only be achieved by nesting folders or by using aliases. Is this correct, or am I missing something?4) What is the current data on how much overhead is caused by using aliases to either files or folders in Webcat and Webstar?I'm not terribly excited about rearranging all our databases (and references to them!) into a 3-level nested configuration to allow database sharing between all our sites and ssl, so I think I would be stuck with aliases in this case.Unless I just stick with Firesite where everything works as it did before, as soon as the dev version stabilizes a bit and stops spewing 200mb debug logs.Comments anyone?Thanks,Dale ________________________ ______________________________ | Dale LaFountain | mailto:dalel@dhorse.com | | MIS Director,WebMaster | web: http://www.dhorse.com/ | | Dark Horse Comics, Inc.|Phone: 503-652-8815 x324 | \________________________|______________________________/
Dale LaFountain
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:
emailer w/F2 (1997)
[WebDNA] Re-sending email (2018)
RE: Template not found error messages (1997)
Protect & InstantSSL (Fixed) (2003)
Digital Postcards (1999)
Questions (1998)
Requiring that certain fields be completed (1997)
[WebDNA] Security Images (Captcha) (2008)
Re1000001: Setting up shop (1997)
Loss in Form (1998)
Protect (1997)
Listserver problem (1997)
[shownext] and descending order (1997)
Up and running ... at last !! (1997)
Search design (1997)
FYI-WebCat Mac or NT (1997)
removing programming logic white space (2003)
Ad Serving Software (2002)
[WebDNA] Processor Maxing out (2010)
Looking for WebCatalog Programmer in Silicon Valley (1998)