Could someone give some clarification on how config.db_cgi_url and config.db_cgi_url_https differ in how they are handled by dynamic mode with respect to preserving the dynamic_preserve fields?
I'm running a site on my main domain, but the SSL portion of the site is under a server wide SSL cert. The system doesn't seem to preserve dynamic fields for those urls.
for example,
I access a url like this: http://mysite.com/page.cgi?d=1&t=luna
my vars are similar to:
<%db_cgi_url%> = http://mysite.com/cgi-bin
<%db_cgi_url_https%> = https://mysite.sslserver.com/cgi-bin/ or
https://mysite.sslserver.com/~username/cgi-bin
The following codes are in my template----->and this is what they become
<%db_cgi_url%>/search.cgi-------------> becomes search.cgi?d=1;t=luna
<%build_root_url%>/-------------------->becomes page.cgi?d=1;g=/;t=luna
<%db_cgi_url_https%>/user.cgi--------->remains user.cgi (this should be user.cgi?d=1;t=luna shouldn't it?)
It appears that form posts get updated properly, just not url links.
Are there plans to support an SSL domain using a sitewide cert?
peace.
k. langan
I'm running a site on my main domain, but the SSL portion of the site is under a server wide SSL cert. The system doesn't seem to preserve dynamic fields for those urls.
for example,
I access a url like this: http://mysite.com/page.cgi?d=1&t=luna
my vars are similar to:
<%db_cgi_url%> = http://mysite.com/cgi-bin
<%db_cgi_url_https%> = https://mysite.sslserver.com/cgi-bin/ or
https://mysite.sslserver.com/~username/cgi-bin
The following codes are in my template----->and this is what they become
<%db_cgi_url%>/search.cgi-------------> becomes search.cgi?d=1;t=luna
<%build_root_url%>/-------------------->becomes page.cgi?d=1;g=/;t=luna
<%db_cgi_url_https%>/user.cgi--------->remains user.cgi (this should be user.cgi?d=1;t=luna shouldn't it?)
It appears that form posts get updated properly, just not url links.
Are there plans to support an SSL domain using a sitewide cert?
peace.
k. langan