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 = 108183
interpreted = N
texte = --0050450180b663e3e604b735986aContent-Type: text/plain; charset=ISO-8859-1On Mon, Jan 23, 2012 at 11:40 AM, Govinda wrote:> I am glad to hear it (sincerely) ... but in my case, on my friend's remote> server.. this one:>> [platform]=unix-Macintosh OS X> (webdna) [version]=6.0>> ... same .htaccess file as my local copy.. BUT we are getting the> *post-RewriteRule* in [thisurl]I'm on Linux/CentOS version 6.2. I don't know about 6.0.Well.. how to determine that ^^^ ? If you mean, "are the contents of> .htaccess the same?" Then, "yes they are the same."That is what I meant. A simple flag change could have affected things.> >> rewriterule is powerful and can do redirects or server-side rewrites> only.>> Yeah, love the power.>> >> If a redirect will work, that is usually preferred.>> for redirect we already have webdna's [redirect].. and, frankly, I prefer> to not touch Apache if I can help it.>I meant rewriterule in apache should be used where redirectmatch does not. That preference is largely due to the complexity of rewriterule which isso robust. I do not know much about webdna's redirect but have used it. Iforget if it is a 301 or 302 but it does change the browser and end webdnaprocessing on the page.> But in the case when one is writing a framework with all kinds of great> practical features, like where we want ALL traffic (to non-existant files)> to come through one central controller file, then server-side rewrite is a> perfect tool.>I see now.> But what I need to know is:>> - which all versions/platforms of Webdna will honor what is in the URL> field of the browser>> ----- versus ------>> - which all versions/platforms of Webdna will not honor what is in the URL> field of the browser (i.e. which versions instead have [thisurl] reflect> what is the result of a *Apache-server-side* RewriteRule, and do NOT> reflect what is in the URL field of the browser).>I shared my experience on Linux CentOS and Mac OS X both with 6.2. TheTHISURL tag returns the browser's address bar. ----- and ------>> - is there anything we can do with Apache config. that will allow us to> cause the latter versions/platforms of Webdna to have [thisurl] always> reflect what is in the URL field of the browser?This would require some checking but I suspect yes. The request_URI wouldneed to provided to webDNA via apache like a variable in a rewrite. Something like:RewriteEngine ONrewriterule regex_to_match /catchallurl.htm?thisurl=%{request_URI}might work. I suspect some experimentation would be required.--0050450180b663e3e604b735986aContent-Type: text/html; charset=ISO-8859-1Content-Transfer-Encoding: quoted-printableOn Mon, Jan 23, 2012 at 11:40 AM, Govinda <govinda.webdnatalk@gmail.com> wrote:

I am glad to hear it (sincerely) ... but in my case, on my friend's rem=ote server.. this one:

[platform]=3Dunix-Macintosh OS X
(webdna) [version]=3D6.0

... same .htaccess file as my local copy.. =A0BUT we are getting the *post-=RewriteRule* in [thisurl]

I&=#39;m on Linux/CentOS version 6.2. =A0I don't know about 6.0. =A0

Well.. how to determine that ^^^ ?= =A0 If you mean, "are the contents of .htaccess the same?" =A0Th=en, "yes they are the same."

That is what I meant. =A0A simple flag change could hav=e affected things. =A0

=A0

>> =A0rewriterule is powerful and can do redirects or server-side rew=rites only.

Yeah, love the power.

>> If a redirect will work, that is usually preferred.

for redirect we already have webdna's [redirect].. and, frankly, =I prefer to not touch Apache if I can help it.

I meant rewriterule in apache should be used where r=edirectmatch does not. =A0That preference is largely due to the complexity =of rewriterule which is so robust. =A0I do not know much about webdna's= redirect but have used it. =A0I forget if it is a 301 or 302 but it does c=hange the browser and end webdna processing on the page. =A0

=A0

But in the case when one is writing a framework with all kinds of great pra=ctical features, like where we want ALL traffic (to non-existant files) to =come through one central controller file, then server-side rewrite is a per=fect tool.

I see now. =A0 =A0

=A0

But what I need to know is:

- which all versions/platforms of Webdna will honor what is in the URL fiel=d of the browser

=A0 =A0 =A0 =A0----- versus ------

- which all versions/platforms of Webdna will not honor what is in the URL =field of the browser (i.e. which versions instead have [thisurl] reflect wh=at is the result of a *Apache-server-side* RewriteRule, and do NOT reflect =what is in the URL field of the browser).

I shared my experience on L=inux CentOS and Mac OS X both with 6.2. =A0The THISURL tag returns the brow=ser's address bar. =A0

=A0

=A0 =A0 =A0 =A0----- and ------

- is there anything we can do with Apache config. that will allow us to cau=se the latter versions/platforms of Webdna to have [thisurl] always reflect= what is in the URL field of the browser?

This would require some checking but I suspect yes. =A0The request_URI woul=d need to provided to webDNA via apache like a variable in a rewrite. =A0So=mething like:=A0

RewriteEngine ON

rewrit=erule regex_to_match /catchallurl.htm?thisurl=3D%{request_URI}

might work. =A0I suspect some experimentation would be =required. =A0

=A0

--0050450180b663e3e604b735986a-- Associated Messages, from the most recent to the oldest:

Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Tom Duke 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Tom Duke 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (William DeVaul 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Tom Duke 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (William DeVaul 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (William DeVaul 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Tom Duke 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (William DeVaul 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (William DeVaul 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Donovan Brooke 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Donovan Brooke 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (William DeVaul 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Donovan Brooke 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (William DeVaul 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)
Re: [WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (christophe.billiottet@webdna.us 2012)
[WebDNA] behavior of [thisurl] in the context of 'mod_rewrite' (Govinda 2012)

--0050450180b663e3e604b735986aContent-Type: text/plain; charset=ISO-8859-1On Mon, Jan 23, 2012 at 11:40 AM, Govinda wrote:> I am glad to hear it (sincerely) ... but in my case, on my friend's remote> server.. this one:>> [platform]=unix-Macintosh OS X> (webdna) [version]=6.0>> ... same .htaccess file as my local copy.. BUT we are getting the> *post-RewriteRule* in [thisurl]I'm on Linux/CentOS version 6.2. I don't know about 6.0.Well.. how to determine that ^^^ ? If you mean, "are the contents of> .htaccess the same?" Then, "yes they are the same."That is what I meant. A simple flag change could have affected things.> >> rewriterule is powerful and can do redirects or server-side rewrites> only.>> Yeah, love the power.>> >> If a redirect will work, that is usually preferred.>> for redirect we already have webdna's [redirect].. and, frankly, I prefer> to not touch Apache if I can help it.>I meant rewriterule in apache should be used where redirectmatch does not. That preference is largely due to the complexity of rewriterule which isso robust. I do not know much about webdna's redirect but have used it. Iforget if it is a 301 or 302 but it does change the browser and end webdnaprocessing on the page.> But in the case when one is writing a framework with all kinds of great> practical features, like where we want ALL traffic (to non-existant files)> to come through one central controller file, then server-side rewrite is a> perfect tool.>I see now.> But what I need to know is:>> - which all versions/platforms of Webdna will honor what is in the URL> field of the browser>> ----- versus ------>> - which all versions/platforms of Webdna will not honor what is in the URL> field of the browser (i.e. which versions instead have [thisurl] reflect> what is the result of a *Apache-server-side* RewriteRule, and do NOT> reflect what is in the URL field of the browser).>I shared my experience on Linux CentOS and Mac OS X both with 6.2. TheTHISURL tag returns the browser's address bar. ----- and ------>> - is there anything we can do with Apache config. that will allow us to> cause the latter versions/platforms of Webdna to have [thisurl] always> reflect what is in the URL field of the browser?This would require some checking but I suspect yes. The request_URI wouldneed to provided to webDNA via apache like a variable in a rewrite. Something like:RewriteEngine ONrewriterule regex_to_match /catchallurl.htm?thisurl=%{request_URI}might work. I suspect some experimentation would be required.--0050450180b663e3e604b735986aContent-Type: text/html; charset=ISO-8859-1Content-Transfer-Encoding: quoted-printableOn Mon, Jan 23, 2012 at 11:40 AM, Govinda <govinda.webdnatalk@gmail.com> wrote: