in.cgi versus te_redirect.php
Posted: Fri Sep 24, 2010 2:16 am
Three things:
1. What is the difference between using in.cgi - and te_redirect.php - and how many times should redirect.php be included on a site.
2. Because there's no knowing what page a visitor is going to arrive on - surely, in.cgi has to go on every site page.
3. I can get the cookie correctly laid down on my php pages, but on my html warning page - the following just seems to be being rendered as a comment and not as an include:
<!--#include virtual="/cgi-bin/te/in.cgi?p=default&$QUERY_STRING" -->
1. What is the difference between using in.cgi - and te_redirect.php - and how many times should redirect.php be included on a site.
2. Because there's no knowing what page a visitor is going to arrive on - surely, in.cgi has to go on every site page.
3. I can get the cookie correctly laid down on my php pages, but on my html warning page - the following just seems to be being rendered as a comment and not as an include:
<!--#include virtual="/cgi-bin/te/in.cgi?p=default&$QUERY_STRING" -->