RE: [PHP] HREFs that can't be

2001-03-05 Thread Boget, Chris
How is 3 different from 1? 1: http://www.somedomain.com/program.php?parm1=value1 3: http://www.somedomain.com/program.php/value1 $PATF_INFO now contains '/value1' Ahh. This is pretty much acceptable to search engines. Even better add: Location /program ForceType application/x-httpd-php

RE: [PHP] HREFs that can't be

2001-03-05 Thread php3
Addressed to: "Boget, Chris" [EMAIL PROTECTED] [EMAIL PROTECTED] ** Reply to note from "Boget, Chris" [EMAIL PROTECTED] Mon, 5 Mar 2001 08:25:25 -0600 This is pretty much acceptable to search engines. Even better add: Location /program ForceType application/x-httpd-php

Re: [PHP] HREFs that can't be

2001-03-02 Thread Carsten Gehling
From: [EMAIL PROTECTED] Sent: Friday, March 02, 2001 9:12 AM Just include the SID as a hidden input. It'll be POSTED to the next page right along with your other variables. There's even a way to configure your php.ini file so that PHP includes the hidden SID for you. I forget which

Re: [PHP] HREFs that can't be

2001-03-02 Thread CC Zona
In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: Also, how would I set the (previously GET) vars up as session variables? I'd have to post to yet another script which would set the session variables and in turn SUBMIT (with just the SESSID this time) to the actual page

RE: [PHP] HREFs that can't be

2001-03-02 Thread Boget, Chris
Just include the SID as a hidden input. It'll be POSTED to the next page right along with your other variables. Right. There's even a way to configure your php.ini file so that PHP includes the hidden SID for you. I forget which setting it is--maybe "trans-id" or something like

RE: [PHP] HREFs that can't be

2001-03-02 Thread Boget, Chris
There are only three places you can pass data without using forms, and using buttons, or images to trigger a POST of the data. 1. Get parameters after a ? 2. Cookies. 3. In the URL itself. How is 3 different from 1? Why do you want to eliminate all get params and cookies? That might

RE: [PHP] HREFs that can't be

2001-03-02 Thread Boget, Chris
That won't work. Clicking on a link does not trigger sending of fields (hidden or not). No? How about: form name=myForm method=post action=... input bla bla bla... /form a href="javascript:document.myForm.submit();"Click here/a a href="#" onclick="document.myForm.submit();return

Re: [PHP] HREFs that can't be

2001-03-02 Thread Robert Vetter
"Boget, Chris" wrote: That won't work. Clicking on a link does not trigger sending of fields (hidden or not). No? How about: form name=myForm method=post action=... input bla bla bla... /form a href="javascript:document.myForm.submit();"Click here/a a href="#"

RE: [PHP] HREFs that can't be

2001-03-02 Thread Boget, Chris
This would require a form for every link and that was something I illustrated earlier as one of the possibilities I had come up with. But it was a possibility that I was trying to avoid... No, you could do following: a href="javascript:document.myForm.action='theLink';document.myF

Re: [PHP] HREFs that can't be

2001-03-02 Thread Robert Vetter
"Boget, Chris" wrote: This would require a form for every link and that was something I illustrated earlier as one of the possibilities I had come up with. But it was a possibility that I was trying to avoid... No, you could do following: a

RE: [PHP] HREFs that can't be

2001-03-02 Thread Boget, Chris
[snip] It is "--enable-trans-sid" and it is turned on. However, the problem is that it doesn't work. :( If the user does not have cookies turned on, the SID will not be sent through to the next page on HREFs (I know you have to do it manually when

Re: [PHP] HREFs that can't be

2001-03-01 Thread CC Zona
In article [EMAIL PROTECTED], [EMAIL PROTECTED] ("Boget, Chris") wrote: a href="/hispage.php?var1=xxxvar2=yyy"Herea/br a href="/otherpage.php"Therea/br a href="/thatpage.php?joe=bob"This Placea/br a href="/lapage.php?this=thathis=hershere=there"That Placea/br --- As you know,

Re: [PHP] HREFs that can't be

2001-03-01 Thread Jaxon
Hi Chris, For my own edification, how are you creating the links dynamically - I need to do something similar ..? As far as removing GET variables, you could just flag variables in a database, that would eliminate the majority of the inter-page stuff. You would still need to leave one session

RE: [PHP] HREFs that can't be

2001-03-01 Thread Boget, Chris
a href="/hispage.php?var1=xxxvar2=yyy"Herea/br a href="/otherpage.php"Therea/br a href="/thatpage.php?joe=bob"This Placea/br a href="/lapage.php?this=thathis=hershere=there"That Placea/br --- As you know, those variables are being passed to the linked page via GET variables. Now,

Re: [PHP] HREFs that can't be

2001-03-01 Thread CC Zona
In article [EMAIL PROTECTED], [EMAIL PROTECTED] ("Boget, Chris") wrote: Also, how would I set the (previously GET) vars up as session variables? I'd have to post to yet another script which would set the session variables and in turn SUBMIT (with just the SESSID this time) to the actual