POST without submit

[zester]

HI all
I would like to pass variables to the next page without them showing up in the URL like you do with POST in a form. My problem is that the page I that will be sending the variables from dose not have a form on it so I cannot send them with POST command. So is there a way to pass variable with hyper link, or on a button press, that hides the variables like POST.

[TechAsh]

You could use hidden fields in a form, and then the visitor will need to click the submit button to move onto the next page.

Something like:

<FORM method="POST" action="nextpage.php">
<INPUT type="hidden" name="something" value="<? $avariable; ?>">
<INPUT type="submit" value="Next ->">
</FORM>

[blu3fire]

or use JavaScript hyperlink isntead of button

<a href="javascript:document.formnamehere.submit()">CLICK HERE</a>

[woiwky]

Personally I would just put the data in the user's session and remove it in the next page. That's a lot easier than having to generate it in the html in my opinion. You could just use:

Page 1:

session_start();
$_SESSION['name'] = 'value'; 

Page 2:

session_start();
$value = $_SESSION['name'];
unset($_SESSION['name']); 

This also means that you don't need to generate more html for every link to a page that you want the use the data in.

By the way, phpasks, what's up with you copying the code/answer people posted before you? You're just restating what's already been said, which is basically spam.

[zester]

I was thinking of using sessions to pass the data but someone told me not to use them. He said it would makes your website unsecure unless you are very good at coding. Is this true?

[konekt]

I was thinking of using sessions to pass the data but someone told me not to use them. He said it would makes your website unsecure unless you are very good at coding. Is this true?

Not particularly true, at least not in the sense that it does not add a significantly extra shaky security then any other methods that introduce dynamic, slightly public, methods (i.e. POST).


You could also use cookies.

[marshian]

Sessions are more secure than cookies, if that really matters for you. A user can edit/delete cookies, but he can only delete sessions.
EDIT: I mean, he can delete the cookie that remembers his session, nothing else

[woiwky]

I was thinking of using sessions to pass the data but someone told me not to use them. He said it would makes your website unsecure unless you are very good at coding. Is this true?

The only more secure way to store the data is to have the user login and store it in the database. But even then, unless you want to make people login for every page they access, you need a way to store who that person is.

Sessions are the most secure way to store temporary data without decreasing your site's usability. The data is stored out of the web root directory(at least it *should* be), which means people can't even view it.

[VPmase]

Even if you were going to use sessions I suggest you create/use some sort of encryption/decryption system so it is secure.

[marshian]

Even if you were going to use sessions I suggest you create/use some sort of encryption/decryption system so it is secure.

Why would it be required? Session data is stored on the server, under a session name. The user only has the session name, so he can't really compromise any data... (You can hijack sessions, but you could solve this by storing the users IP with the session information. (If the stored ip and the user's ip don't match, destroy the session and make the user verify himself again.))