Can I build into a POST, along with the URL encoded string, the HTTP Referrer... (into the http header, presumably) Or, will the HTTP header only carry the referrer which is the domain name of the ISP that actually handles the post? scenario: stack is on a CD in someone's computer or on someone's harddrive...the stack has a "registration form" which POSTs data to a cgi on a distant server...can we control who the distant server (where the CGI lives,) perceives to be the referrer? Or will that CGI automatically register the domain name of the ISP through which the POST is passed, regardless of what we put into the http header? Yes, presumably this would be trivial to test...assuming I knew a) how to build a complete HTTP header and b) I could get a .mt script to pass back to standout the full http data , and not just the string... Neither of which I know how to do. Flame away if you think I should not be asking these questions on this list... Hinduism Today Sivakatirswami Editor's Assistant/Production Manager [EMAIL PROTECTED] www.HinduismToday.com, www.HimalayanAcademy.com, www.Gurudeva.org, www.hindu.org Archives: http://www.mail-archive.com/[email protected]/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to <[EMAIL PROTECTED]>, not this list.
