Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite'
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108154
interpreted = N
texte = >> Do you know how to control when mod_rewrite kicks in? We could use = some help with this level of apache admin. Apparently, we want = mod_rewrite to kick in *after* webdna gets the file.. but at the moment = the reverse is happening. >>=20 >> Or, wait a minute.. this makes no sense. If apache tried to hand = the file to webdna before mod_rewrite kicked in then I would not see = anything resembling my page in the browser because the URL is pointing = to a *non-existent* file. The fact that the file is non-exitant is the = very reason I want to use mod_rewrite. My RewriteRule causes the URL = to become re_written to point to a real existent webdna file. >>=20 >> AFAICT mod_rewrite *has to be* (in both my local and remote cases) = kicking in before webdna gets the file.. because my file IS being parsed = by webdna and spitting out the expected dynamic HTML output... the only = problem is that in the remote-server case [thisurl] reflects the = *post-RewriteRule* URL, as opposed to the *pre-RewriteRule* URL. Maybe = that is expected behavior... but then why on my local setup does = [thisurl] reflect the *pre-RewriteRule* URL?! >>=20 >> Would anyone be willing to setup up a test case and see what you = find.. set up mod_rewrite and a RewriteRule in .htaccess which points = a sample URL like this non-existent page: = 'domain.com/testDIR_A/testPAGE_A.html' ... to your existent page: = 'domain.com/testDIR_B/testPAGE_B.html' page... and then inspect the = output of [thisurl] to see what you get. And while reporting findings, = please mention if your test was on your localhost setup, or was it on a = remote server? I would like to know the results of both if possible. >>=20 >> The results of all this is something I am trying to finish off in the = next couple days and share with the group here.. something nice and = really worthwhile. >>=20 >> Thanks! >>=20 >> -Govinda > The incoming http request goes: >=20 > browser -> Internet -> server (machine) -> apache (web server = responsible for port at IP address) -> webdna (assuming file extension = under webdna control) >=20 > I think you can control what the browser sees if you send a 301 = (permanently moved) in response to the rewrite. Otherwise the rewrite = is invisible to the browser. I'm just guessing here, but some rewrites = should be known and others are for internal purposes only. =20 >=20 > Bill I have question, ideas, possible solutions... but meanwhile, I really want to answer this one simple question: * WHY, on my local Apache setup on MacOS 10.6 / Webdna 7, is [thisurl] = reflecting the *pre-RewriteRule* URL? * I need to emulate this. What do you advise for trying to accomplish this? Can you point in the = direction of an example line in .htaccess, if that is what we are = talking about? And/Or, I might understand this better, if I could see an example: "...send a 301 (permanently moved) in response to the rewrite.." Thanks -Govinda=
Associated Messages, from the most recent to the oldest:
>> Do you know how to control when mod_rewrite kicks in? We could use = some help with this level of apache admin. Apparently, we want = mod_rewrite to kick in *after* webdna gets the file.. but at the moment = the reverse is happening. >>=20 >> Or, wait a minute.. this makes no sense. If apache tried to hand = the file to webdna before mod_rewrite kicked in then I would not see = anything resembling my page in the browser because the URL is pointing = to a *non-existent* file. The fact that the file is non-exitant is the = very reason I want to use mod_rewrite. My RewriteRule causes the URL = to become re_written to point to a real existent webdna file. >>=20 >> AFAICT mod_rewrite *has to be* (in both my local and remote cases) = kicking in before webdna gets the file.. because my file IS being parsed = by webdna and spitting out the expected dynamic HTML output... the only = problem is that in the remote-server case
[thisurl] reflects the = *post-RewriteRule* URL, as opposed to the *pre-RewriteRule* URL. Maybe = that is expected behavior... but then why on my local setup does =
[thisurl] reflect the *pre-RewriteRule* URL?! >>=20 >> Would anyone be willing to setup up a test case and see what you = find.. set up mod_rewrite and a RewriteRule in .htaccess which points = a sample URL like this non-existent page: = 'domain.com/testDIR_A/testPAGE_A.html' ... to your existent page: = 'domain.com/testDIR_B/testPAGE_B.html' page... and then inspect the = output of
[thisurl] to see what you get. And while reporting findings, = please mention if your test was on your localhost setup, or was it on a = remote server? I would like to know the results of both if possible. >>=20 >> The results of all this is something I am trying to finish off in the = next couple days and share with the group here.. something nice and = really worthwhile. >>=20 >> Thanks! >>=20 >> -Govinda > The incoming http request goes: >=20 > browser -> Internet -> server (machine) -> apache (web server = responsible for port at IP address) -> webdna (assuming file extension = under webdna control) >=20 > I think you can control what the browser sees if you send a 301 = (permanently moved) in response to the rewrite. Otherwise the rewrite = is invisible to the browser. I'm just guessing here, but some rewrites = should be known and others are for internal purposes only. =20 >=20 > Bill I have question, ideas, possible solutions... but meanwhile, I really want to answer this one simple question: * WHY, on my local Apache setup on MacOS 10.6 / Webdna 7, is
[thisurl] = reflecting the *pre-RewriteRule* URL? * I need to emulate this. What do you advise for trying to accomplish this? Can you point in the = direction of an example line in .htaccess, if that is what we are = talking about? And/Or, I might understand this better, if I could see an example: "...send a 301 (permanently moved) in response to the rewrite.." Thanks -Govinda=
Govinda
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:
First n words (2000)
PIXO support (1997)
Help! WebCat2 bug (1997)
WebCatalog for guestbook ? (1997)
Introduction/Tutorial/QuickStart (1997)
[math] are you there? (1999)
Running _every_ page through WebCat ? (1997)
Grant, please help me ... (1997)
Nesting format tags (1997)
Re:listfiles-looking for slick solution (1997)
ShowNext Page Style (2003)
NT considerations (1997)
Sorting Numbers (1997)
WCS Newbie question (1997)
Taxable Shipping (2003)
Re:upgrade problem with users.db (1998)
expansion domain freak out (2003)
Re:Searching for ALL / empty form field (1997)
[WriteFile] problems (1997)
Running WebCat from a CD-ROM (1997)