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

Having your ssl on a separate domain isn't going to work because cookies aren't going to be valid on that domain (thus the user gets logged out).

Adrian

Thanks for the response brewt, but that's not the issue as I'm only talking about d and t parameters. The point you make about users is a bridge I have to cross later, more than likely by using urls to pass my session.

the issue is really when d=1 and t=luna then d and t should remain regardless of whether I'm accessing the site via db_cgi_url_https or db_cgi_url. It seems to work for forms (haven't tried GET) but not for URLs.

peace.

k. langan

That's happening because the dynamic preserve only works on certain url's (look at Links::clean_output) and the https url isn't one of them (and we sort of can't because it's created dynamically if it isn't set). However, for future versions, I've added a form_hidden template variable for cases where clean_output doesn't dynamically insert it for you.

Adrian

Hi Brewt,

thanks for the info. I found url_hidden which is what I need, but unless you mean you've just added form_hidden, it didn't come up in GT::Template:dump. Again though <%url_hidden%> is exactly what's needed in my situations, so thanks for letting me know that.

peace.

k.langan

It depends on what you're doing. url_hidden will do what you need if you need it for appending the extra args to a url, form_hidden is what you need if it's a form being submitted (which will be added in the next release).

Adrian