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 = 108287
interpreted = N
texte = Tom, > ...is the form using an 'enctype' of 'multipart/form-data' ? no. just a regular ole form. You remind me that I do need to see what happens with = multipart/form-data.. and I'll report about that later, in case I do = not see a way to hack it quick and easy myself. Bill, > Can you change the form from POST to GET and see what happens? =20 When I change the form's method to GET, then the RewriteRule's = '%{REQUEST_URI}' *does* get passed into webdna space as [REQUEST_URI],=20= (via: RewriteRule ^(.*)$ index.dna?REQUEST_URI=3D%{REQUEST_URI} [L] ),=20 ..and the submitted formvars do come in via the URL.. but that is not = going to be a solution because we don't want GET method which sticks = everything in the URL ;-) ... and also not going to work for other = reasons specific to the code I am working on.. which is not worth = explaining just here/now. > I suspect you may be right about the POSTed information not being = passed in the rewrite but that seems odd to me. =20 well it is the other way around; the form-POSTed data DOES get passed, = but the [REQUEST_URI], (via: RewriteRule ^(.*)$ index.dna?REQUEST_URI=3D%{REQUEST_URI} [L] ),=20 ...does NOT get passed. =20 IOW, if I have a form input like so in my form: then inside the landing page's = [formvariables][name]=3D[vaue][/formvariables] context, I see: "hello=3Dworld" but I do NOT see "REQUEST_URI=3D((the URL we posted to))" There is no [REQUEST_URI] var at all. My original question: Is there something like %{REQUEST_URI} in apache directives.. but which = is automagically populated by *either* %{REQUEST_URI}, or else by the = pre-RewriteRule URL segments (after the domain) *upon form post*? =20 Thanks guys, -Govinda
Associated Messages, from the most recent to the oldest:
Tom, > ...is the form using an 'enctype' of 'multipart/form-data' ? no. just a regular ole form. You remind me that I do need to see what happens with = multipart/form-data.. and I'll report about that later, in case I do = not see a way to hack it quick and easy myself. Bill, > Can you change the form from POST to GET and see what happens? =20 When I change the form's method to GET, then the RewriteRule's = '%{REQUEST_URI}' *does* get passed into webdna space as [REQUEST_URI],=20= (via: RewriteRule ^(.*)$ index.dna?REQUEST_URI=3D%{REQUEST_URI} [L] ),=20 ..and the submitted formvars do come in via the URL.. but that is not = going to be a solution because we don't want GET method which sticks = everything in the URL ;-) ... and also not going to work for other = reasons specific to the code I am working on.. which is not worth = explaining just here/now. > I suspect you may be right about the POSTed information not being = passed in the rewrite but that seems odd to me. =20 well it is the other way around; the form-POSTed data DOES get passed, = but the [REQUEST_URI], (via: RewriteRule ^(.*)$ index.dna?REQUEST_URI=3D%{REQUEST_URI} [L] ),=20 ...does NOT get passed. =20 IOW, if I have a form input like so in my form: then inside the landing page's = [formvariables][name]=3D[vaue][/formvariables] context, I see: "hello=3Dworld" but I do NOT see "REQUEST_URI=3D((the URL we posted to))" There is no [REQUEST_URI] var at all. My original question: Is there something like %{REQUEST_URI} in apache directives.. but which = is automagically populated by *either* %{REQUEST_URI}, or else by the = pre-RewriteRule URL segments (after the domain) *upon form post*? =20 Thanks guys, -Govinda
Govinda
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...