Re: [WebDNA] Windows FastCGI thisurl issues
This WebDNA talk-list message is from 2018
It keeps the original formatting.
numero = 114463
interpreted = N
texte = 2082 Hi Matthew! We spent quite a bit of time looking at the Windows / vs \ issue today = and yesterday. It is complicated. I don=E2=80=99t think the behavior has = changed: \ and / are interchangeable on Windows, except when the at the very = beginning of the filename. For example: [INCLUDE FILE=3D../dir1/myfile.dna] and [INCLUDE = FILE=3D..\dir1\myfile.dna] work the same. [INCLUDE FILE=3D/dir1/myfile.dna] and [INCLUDE FILE=3D\dir1\myfile.dna] = do not work the same. Any filename beginning with / on the older Windows Server versions had a = special behavior. / is treated as being the "engine" directory. On the = old Windows Server version, this would be the directory that contains = DBServer.exe. The new Windows FastCGI version kept this special = behavior, and looks in the directory containing WebDNA.exe when a = filename begins with /. The OSX and Linux FastCGI and Server versions do not use the engine = directory for /. They use the document root for / (aka, the root = location of the website files for the current website). 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 OSes. If the current file is executing from the document = root, then /myfile.dna and \myfile.dna are interchangeable on Linux and = OSX. If you are in a subdirectory of the document root, then /myfile.dna = and \myfile.dna point to different locations. I feel right now the behavior is actually more compatible with the old = Windows Server version. We can easily change it to be like the other versions. This might make = more sense to keep everything consistent. Opinions welcomed=E2=80=A6 - chris > On Sep 27, 2018, at 15:37, Buske, Matthew
= wrote: >=20 > Hello, > =20 > We have been playing with the Windows FastCGI 8.6.1 to see if it is an = option for our migration from the Windows 6.2 server version. We have = noticed though that the thisurl and thisurlplusget tag seem to return = nothing- wondering if anyone else has experienced this issue on Windows. > =20 > Also, we have noticed that the =E2=80=98/=E2=80=99 and =E2=80=98\=E2=80=99= file separators function differently than in the previous version. In = 6.2, both could be used interchangeably where as in 8.6.1 =E2=80=98\=E2=80= =99 seems to be used for the root path and =E2=80=98/=E2=80=99 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. > =20 > Thanks for all the help! > =20 > Matthew Buske > Database Administrator > Center for Instruction, Technology & Innovation --------------------------------------------------------- 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:
2082 Hi Matthew! We spent quite a bit of time looking at the Windows / vs \ issue today = and yesterday. It is complicated. I don=E2=80=99t think the behavior has = changed: \ and / are interchangeable on Windows, except when the at the very = beginning of the filename. For example: [INCLUDE FILE=3D../dir1/myfile.dna] and [INCLUDE = FILE=3D..\dir1\myfile.dna] work the same. [INCLUDE FILE=3D/dir1/myfile.dna] and [INCLUDE FILE=3D\dir1\myfile.dna] = do not work the same. Any filename beginning with / on the older Windows Server versions had a = special behavior. / is treated as being the "engine" directory. On the = old Windows Server version, this would be the directory that contains = DBServer.exe. The new Windows FastCGI version kept this special = behavior, and looks in the directory containing WebDNA.exe when a = filename begins with /. The OSX and Linux FastCGI and Server versions do not use the engine = directory for /. They use the document root for / (aka, the root = location of the website files for the current website). 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 OSes. If the current file is executing from the document = root, then /myfile.dna and \myfile.dna are interchangeable on Linux and = OSX. If you are in a subdirectory of the document root, then /myfile.dna = and \myfile.dna point to different locations. I feel right now the behavior is actually more compatible with the old = Windows Server version. We can easily change it to be like the other versions. This might make = more sense to keep everything consistent. Opinions welcomed=E2=80=A6 - chris > On Sep 27, 2018, at 15:37, Buske, Matthew = wrote: >=20 > Hello, > =20 > We have been playing with the Windows FastCGI 8.6.1 to see if it is an = option for our migration from the Windows 6.2 server version. We have = noticed though that the thisurl and thisurlplusget tag seem to return = nothing- wondering if anyone else has experienced this issue on Windows. > =20 > Also, we have noticed that the =E2=80=98/=E2=80=99 and =E2=80=98\=E2=80=99= file separators function differently than in the previous version. In = 6.2, both could be used interchangeably where as in 8.6.1 =E2=80=98\=E2=80= =99 seems to be used for the root path and =E2=80=98/=E2=80=99 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. > =20 > Thanks for all the help! > =20 > Matthew Buske > Database Administrator > Center for Instruction, Technology & Innovation --------------------------------------------------------- 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 .
christophe.billiottet@webdna.us
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:
pc (1997)
WebSite vs. IIS (1997)
WCS Newbie question (1997)
Is the Finder required? (1998)
Trouble with formula.db (1997)
Upgrading old WebCat Database Files (1997)
Showif, Hideif reverse logic ? (1997)
NT or Mac (1998)
[WebDNA] lighttpd problem with returnraw http header (2018)
Alternating colors (1997)
Date Formats (1997)
RE: Ongoing group search problems ... (1997)
Bug Report, maybe (1997)
cookies and [returnraw] (1997)
Signal Raised Error (Part II) (1997)
Cart Number sequence (1997)
[writefile] (1997)
Authenticate (1997)
[WebDNA] How to code a 301 redirect (2008)
can you reassign loop index? (1998)