Re: [WebDNA] Different results for [THISURL]
This WebDNA talk-list message is from 2018
It keeps the original formatting.
numero = 114430
interpreted = N
texte = 2049Yes, we will write 2 new installers (fastCGI and server) that will1.- disable Mojave's apache2.- install a pristine apache version3.- ask to the user the website(s) names he/she wants to create inside =/Documents/4.- configure apache and WebDNA.fcgi or WebDNA serverThe installer will be able to run at a later time to install new =websites.This installer will work on a client OSX Mojave but not the OSX server =version: far too complicated just to remove apache: the server/proxy =would basically stop working.- chris> On Oct 12, 2018, at 12:38, Stuart Tremain
=wrote:>=20> Thanks for the explanation on what is happening here.=20>=20> Are there any work arounds or when do you think that this may be =available in the server edition?>=20> Regards> Stuart Tremain>=20> Pharoah Lane Software=20> 7/76 Reserve Road=20> Artarmon NSW 2064> AUSTRALIA> +612 8971 4431>=20>> On 8 Oct 2018, at 4:54 pm, christophe.billiottet@webdna.us wrote:>>=20>> Hi Stuart,>>=20>> yes, I think this should be fixed, the behavior isn=E2=80=99t =consistent when mod_rewrite rules are involved.>>=20>> I wonder if you have it backwards though, I guess the FastCGI version =always shows /department/category because it generates THISURL from the =REQUEST_URI parameter, and this should be the original URL without the =domain name in front.>>=20>> Whereas, the Server version's module uses Apache's =request_rec->unparsed_uri. The issue I'm seeing is that unparsed_uri =will be /department/category if your mod_rewrite rules are in your main =apache config files. But if you have your mod_rewrite rules in a =..htaccess file, then Apache generates a new request and it puts the =rewritten URL (/dept-root/cat-page.html) in unparsed_uri.>>=20>> I think the solution would be to adjust the Server module to always =generate THISURL from the raw request. We will do it.>>=20>> If you see /dept-root/cat-page.html with the FastCGI version, then I =would be interested in knowing if you are using Apache+mod_fcgid or =something else. We could not reproduce this with latest WebDNA =FastCGI+Apache+mod_fcgid on Ubuntu.>>=20>> kind regards,>>=20>> - chris---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us.
Associated Messages, from the most recent to the oldest:
2049Yes, we will write 2 new installers (fastCGI and server) that will1.- disable Mojave's apache2.- install a pristine apache version3.- ask to the user the website(s) names he/she wants to create inside =/Documents/4.- configure apache and WebDNA.fcgi or WebDNA serverThe installer will be able to run at a later time to install new =websites.This installer will work on a client OSX Mojave but not the OSX server =version: far too complicated just to remove apache: the server/proxy =would basically stop working.- chris> On Oct 12, 2018, at 12:38, Stuart Tremain =wrote:>=20> Thanks for the explanation on what is happening here.=20>=20> Are there any work arounds or when do you think that this may be =available in the server edition?>=20> Regards> Stuart Tremain>=20> Pharoah Lane Software=20> 7/76 Reserve Road=20> Artarmon NSW 2064> AUSTRALIA> +612 8971 4431>=20>> On 8 Oct 2018, at 4:54 pm, christophe.billiottet@webdna.us wrote:>>=20>> Hi Stuart,>>=20>> yes, I think this should be fixed, the behavior isn=E2=80=99t =consistent when mod_rewrite rules are involved.>>=20>> I wonder if you have it backwards though, I guess the FastCGI version =always shows /department/category because it generates THISURL from the =REQUEST_URI parameter, and this should be the original URL without the =domain name in front.>>=20>> Whereas, the Server version's module uses Apache's =request_rec->unparsed_uri. The issue I'm seeing is that unparsed_uri =will be /department/category if your mod_rewrite rules are in your main =apache config files. But if you have your mod_rewrite rules in a =..htaccess file, then Apache generates a new request and it puts the =rewritten URL (/dept-root/cat-page.html) in unparsed_uri.>>=20>> I think the solution would be to adjust the Server module to always =generate THISURL from the raw request. We will do it.>>=20>> If you see /dept-root/cat-page.html with the FastCGI version, then I =would be interested in knowing if you are using Apache+mod_fcgid or =something else. We could not reproduce this with latest WebDNA =FastCGI+Apache+mod_fcgid on Ubuntu.>>=20>> kind regards,>>=20>> - chris---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug 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:
Help formatting search results w/ table (1997)
webcat- multiple selection in input field (1997)
Ampersand (1997)
Disappearing data [OT] (2002)
SMSI - MacWorld (2005)
PCS Emailer's role ? (1997)
b12 cannot limit records returned and more. (1997)
[WebDNA] Live Currency exchanege rates (2008)
Redirect frame targets (1998)
bug in [SendMail] (1997)
OT: javascript print() (2003)
Nested vs conditional (1997)
File Upload (1997)
FRAMES and CART tags problem??!? (1999)
A multi-processor savvy WebCatalog? (1997)
Add a field to the error log? (1997)
4.x in production update (2000)
Apoligy (1997)
PSC recommends what date format yr 2000??? (1997)
[OT]Target Links (advanced??) (2001)