how to prevent the GET vars from transferring to the next continuously

[tigeress]

I wrote a php program which manage a database.
It shows the records and contains hotlinks "Edit" which links itself with some GET variables.If I click the hotlink "Edit" of one record,it will show a form to show the content of the record to edit.When I submit the form,it will run itself with some POST variables.To my surprise,the GET variables transferred from the previous web page are transferred to the next web page.I do not need the result because this will make it difficult to control the logic of the php program,so I wish I can prevent the GET variables from transferring to the next web page continuously.Who can help me?

[laserlight]

Check the form's action attribute.
Is the query string included there?

Of course, if you rely strictly on the $POST and $GET arrays, you probably wont be affected by rogue incoming variables.

[tigeress]

Thanks for your help!
when I click the "edit" hotlink,the url is:
[url]http://.../test.php?caseno=2&delete=0&edit=1[/url]

then it shows a form to edit the record which caseno field is 2.After changed some contents I clicked the submit button,It shows variables as following:

POST:
caseno=2
casetype=1
...

submit=submit

GET:
caseno=2
delete=0

edit=1

...

this means the GET variables from previous web page can be transferred to the next.I wish the three GET variables disappear when I click the submit button.

the form action is :
<form METHOD="POST" ACTION="<?php echo $PHP_SELF?>">

[Shrike]

Because you use $PHP_SELF to set the form action, the entire URL is getting copied in, including the query string. I thought that the POST vars would overwrite it but I might be wrong 🙂

[laserlight]

Originally posted by Shrike
Because you use $PHP_SELF to set the form action, the entire URL is getting copied in, including the query string. I thought that the POST vars would overwrite it but I might be wrong 🙂

To my knowledge it is REQUEST_URI, not PHP_SELF that includes the query string.

I'm not sure exactly what is the problem, though.