RE: [WebDNA] Windows FastCGI thisurl issues
This WebDNA talk-list message is from 2018
It keeps the original formatting.
numero = 114464
interpreted = N
texte = 2083 Hi Chris,=0A= =0A= Thanks so much for looking into this! I did some digging on my end, and aft= er some testing I found the source of my confusion. It seems our win server= is set up with a sandbox that points to the web root. When I started worki= ng with the system I was told that was a quirk of the windows setup- but se= ems it is really to emulate the way Linux and OSX treat '/'. Running a scri= pt consisting of a listfiles for '/' and '\' in my web root resulted in the= same exact list of files. Once we disabled and removed the sandbox and ran= the script again I finally saw the special behavior you described- one lis= ted the location of the web root while the other listed the contents in the= engine directory!=0A= =0A= As there are no sandboxes in the FastCGI, is there a way to emulate via set= tings/configuration without implementing the whole sandbox so that we can k= eep the behavior when needed (or is there a possibility of a new server ver= sion- a big ask I am sure, but that would be really awesome)? While I agree= that keeping the FastCGI and server version of Windows consistent, one of = the big benefits to our setup is we can move between Windows and Linux as n= eeded without worrying about the path structures. =0A= =0A= Again, thanks for your help! I am excited to finally dig into some of the n= ewer features on Windows!=0A= =0A= Matthew Buske=0A= =0A= =0A= ________________________________________=0A= From: christophe.billiottet@webdna.us [christophe.billiottet@webdna.us]=0A= Sent: Friday, November 09, 2018 3:03 PM=0A= To:
=0A= Subject: Re: [WebDNA] Windows FastCGI thisurl issues=0A= =0A= Hi Matthew!=0A= =0A= We spent quite a bit of time looking at the Windows / vs \ issue today and = yesterday. It is complicated. I don=92t think the behavior has changed:=0A= =0A= \ and / are interchangeable on Windows, except when the at the very beginni= ng of the filename. For example:=0A= [INCLUDE FILE=3D../dir1/myfile.dna] and [INCLUDE FILE=3D..\dir1\myfile.dna]= work the same.=0A= [INCLUDE FILE=3D/dir1/myfile.dna] and [INCLUDE FILE=3D\dir1\myfile.dna] do = not work the same.=0A= =0A= Any filename beginning with / on the older Windows Server versions had a sp= ecial behavior. / is treated as being the "engine" directory. On the old Wi= ndows Server version, this would be the directory that contains DBServer.ex= e. The new Windows FastCGI version kept this special behavior, and looks in= the directory containing WebDNA.exe when a filename begins with /.=0A= =0A= The OSX and Linux FastCGI and Server versions do not use the engine directo= ry for /. They use the document root for / (aka, the root location of the w= ebsite files for the current website).=0A= =0A= Any path beginning with \ does not receive special treatment on Windows or = any other OS. It is simply appended to the "here" path, in other words the = current directory the .dna file is opened from. This is the case on all OSe= s. If the current file is executing from the document root, then /myfile.dn= a and \myfile.dna are interchangeable on Linux and OSX. If you are in a sub= directory of the document root, then /myfile.dna and \myfile.dna point to d= ifferent locations.=0A= =0A= =0A= I feel right now the behavior is actually more compatible with the old Wind= ows Server version.=0A= =0A= We can easily change it to be like the other versions. This might make more= sense to keep everything consistent.=0A= =0A= Opinions welcomed=85=0A= =0A= - chris=0A= =0A= =0A= =0A= =0A= > On Sep 27, 2018, at 15:37, Buske, Matthew wrote:= =0A= >=0A= > Hello,=0A= >=0A= > We have been playing with the Windows FastCGI 8.6.1 to see if it is an op= tion for our migration from the Windows 6.2 server version. We have noticed= though that the thisurl and thisurlplusget tag seem to return nothing- won= dering if anyone else has experienced this issue on Windows.=0A= >=0A= > Also, we have noticed that the =91/=92 and =91\=92 file separators functi= on differently than in the previous version. In 6.2, both could be used int= erchangeably where as in 8.6.1 =91\=92 seems to be used for the root path a= nd =91/=92 seems to be the relative path of the file. Before we start doing= the heavy lift of updating the paths in our code I was curious if this was= intentional or if it is something that can be adjusted.=0A= >=0A= > Thanks for all the help!=0A= >=0A= > Matthew Buske=0A= > Database Administrator=0A= > Center for Instruction, Technology & Innovation=0A= =0A= =0A= =0A= =0A= ---------------------------------------------------------=0A= This message is sent to you because you are subscribed to=0A= the mailing list talk@webdna.us=0A= To unsubscribe, E-mail to: talk-leave@webdna.us=0A= archives: http://www.webdna.us/page.dna?numero=3D55=0A= Bug Reporting: support@webdna.us=0A= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
2083 Hi Chris,=0A= =0A= Thanks so much for looking into this! I did some digging on my end, and aft= er some testing I found the source of my confusion. It seems our win server= is set up with a sandbox that points to the web root. When I started worki= ng with the system I was told that was a quirk of the windows setup- but se= ems it is really to emulate the way Linux and OSX treat '/'. Running a scri= pt consisting of a listfiles for '/' and '\' in my web root resulted in the= same exact list of files. Once we disabled and removed the sandbox and ran= the script again I finally saw the special behavior you described- one lis= ted the location of the web root while the other listed the contents in the= engine directory!=0A= =0A= As there are no sandboxes in the FastCGI, is there a way to emulate via set= tings/configuration without implementing the whole sandbox so that we can k= eep the behavior when needed (or is there a possibility of a new server ver= sion- a big ask I am sure, but that would be really awesome)? While I agree= that keeping the FastCGI and server version of Windows consistent, one of = the big benefits to our setup is we can move between Windows and Linux as n= eeded without worrying about the path structures. =0A= =0A= Again, thanks for your help! I am excited to finally dig into some of the n= ewer features on Windows!=0A= =0A= Matthew Buske=0A= =0A= =0A= ________________________________________=0A= From: christophe.billiottet@webdna.us [christophe.billiottet@webdna.us]=0A= Sent: Friday, November 09, 2018 3:03 PM=0A= To: =0A= Subject: Re: [WebDNA] Windows FastCGI thisurl issues=0A= =0A= Hi Matthew!=0A= =0A= We spent quite a bit of time looking at the Windows / vs \ issue today and = yesterday. It is complicated. I don=92t think the behavior has changed:=0A= =0A= \ and / are interchangeable on Windows, except when the at the very beginni= ng of the filename. For example:=0A= [INCLUDE FILE=3D../dir1/myfile.dna] and [INCLUDE FILE=3D..\dir1\myfile.dna]= work the same.=0A= [INCLUDE FILE=3D/dir1/myfile.dna] and [INCLUDE FILE=3D\dir1\myfile.dna] do = not work the same.=0A= =0A= Any filename beginning with / on the older Windows Server versions had a sp= ecial behavior. / is treated as being the "engine" directory. On the old Wi= ndows Server version, this would be the directory that contains DBServer.ex= e. The new Windows FastCGI version kept this special behavior, and looks in= the directory containing WebDNA.exe when a filename begins with /.=0A= =0A= The OSX and Linux FastCGI and Server versions do not use the engine directo= ry for /. They use the document root for / (aka, the root location of the w= ebsite files for the current website).=0A= =0A= Any path beginning with \ does not receive special treatment on Windows or = any other OS. It is simply appended to the "here" path, in other words the = current directory the .dna file is opened from. This is the case on all OSe= s. If the current file is executing from the document root, then /myfile.dn= a and \myfile.dna are interchangeable on Linux and OSX. If you are in a sub= directory of the document root, then /myfile.dna and \myfile.dna point to d= ifferent locations.=0A= =0A= =0A= I feel right now the behavior is actually more compatible with the old Wind= ows Server version.=0A= =0A= We can easily change it to be like the other versions. This might make more= sense to keep everything consistent.=0A= =0A= Opinions welcomed=85=0A= =0A= - chris=0A= =0A= =0A= =0A= =0A= > On Sep 27, 2018, at 15:37, Buske, Matthew wrote:= =0A= >=0A= > Hello,=0A= >=0A= > We have been playing with the Windows FastCGI 8.6.1 to see if it is an op= tion for our migration from the Windows 6.2 server version. We have noticed= though that the thisurl and thisurlplusget tag seem to return nothing- won= dering if anyone else has experienced this issue on Windows.=0A= >=0A= > Also, we have noticed that the =91/=92 and =91\=92 file separators functi= on differently than in the previous version. In 6.2, both could be used int= erchangeably where as in 8.6.1 =91\=92 seems to be used for the root path a= nd =91/=92 seems to be the relative path of the file. Before we start doing= the heavy lift of updating the paths in our code I was curious if this was= intentional or if it is something that can be adjusted.=0A= >=0A= > Thanks for all the help!=0A= >=0A= > Matthew Buske=0A= > Database Administrator=0A= > Center for Instruction, Technology & Innovation=0A= =0A= =0A= =0A= =0A= ---------------------------------------------------------=0A= This message is sent to you because you are subscribed to=0A= the mailing list talk@webdna.us=0A= To unsubscribe, E-mail to: talk-leave@webdna.us=0A= archives: http://www.webdna.us/page.dna?numero=3D55=0A= Bug Reporting: support@webdna.us=0A= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us .
"Buske, Matthew"
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:
wc 2 pro users - sites, quotes wanted (1997)
Locking up with WebCatalog... (1997)
My new discussion forum (2003)
using showpage and showcart commands (1996)
[date] problem with %d%m%Y (1998)
can WC render sites out? (1997)
pop up menu's (1998)
creating a 60 fields database (1997)
Nav. 4 probs with cart (1997)
error message (1998)
shipcost (1997)
[include file] wrong path or syntax when using / referingtoothe root (2002)
encrypt/decrypt failing (2000)
[OT] Happy Turkey Day! (2003)
showif comparison begins w/ and contains (1997)
DNS Lookup 2 (2000)
[OSX] Creative Page (2003)
too many nested [xxx] (1997)
PCS Frames-Default page is solution! (1997)
OT: Website Promotion (1998)