On Fri, April 6, 2007 7:35 pm, barophobia wrote:
I only know of one reason to submit a form as POST and that is because
you can submit more data in one shot.
What other reasons are there?
#1
If it changes anything [*] on the server it MUST be POST and not GET.
If you don't grak this, put it
On Fri, April 6, 2007 7:44 pm, Mike Shanley wrote:
With POST, everything stays hidden, mostly untamperable, and
I must take exception to this statement...
Step 1.
Use your browser's Save As... menu to save the HTML FORM page to
your hard drive.
Step 2.
Change any damn thing you want in the
On 4/7/07, Paul Novitski [EMAIL PROTECTED] wrote:
barophobia wrote:
I only know of one reason to submit a form as POST and that is because
you can submit more data in one shot.
At 4/6/2007 05:44 PM, Mike Shanley wrote:
When you submit via GET, all the info shows up in the URL, so people
can
On Saturday 07 April 2007 05:56, Paul Novitski wrote:
barophobia wrote:
I only know of one reason to submit a form as POST and that is because
you can submit more data in one shot.
At 4/6/2007 05:44 PM, Mike Shanley wrote:
When you submit via GET, all the info shows up in the URL, so people
barophobia wrote:
I only know of one reason to submit a form as POST and that is because
you can submit more data in one shot.
What other reasons are there?
The difference between get and post is not what you *can* do, it's what
you *should* do.
Get, as the name implies, should be used
]
To: php-general php-general@lists.php.net
Sent: Saturday, April 07, 2007 2:35 AM
Subject: [PHP] Submitting as POST. Why?
My Peeps,
I only know of one reason to submit a form as POST and that is because
you can submit more data in one shot.
What other reasons are there?
Chris.
--
PHP
On Sat, 2007-04-07 at 11:10 +0100, Stut wrote:
These implied rules have existed since HTTP was invented, and when you
think about it they make a lot of sense. They also get emphasized by the
existance of so-called web accelerators that simply pre-fetch URLs on
the page the user is viewing.
Robert Cummings wrote:
On Sat, 2007-04-07 at 11:10 +0100, Stut wrote:
These implied rules have existed since HTTP was invented, and when you
think about it they make a lot of sense. They also get emphasized by the
existance of so-called web accelerators that simply pre-fetch URLs on
the page
On Sat, 2007-04-07 at 13:59 +0100, Stut wrote:
Robert Cummings wrote:
On Sat, 2007-04-07 at 11:10 +0100, Stut wrote:
These implied rules have existed since HTTP was invented, and when you
think about it they make a lot of sense. They also get emphasized by the
existance of so-called web
At 9:11 PM -0400 4/6/07, Robert Cummings wrote:
On Fri, 2007-04-06 at 20:44 -0400, Mike Shanley wrote:
With POST, everything stays hidden, mostly untamperable, and
Bullshit. It is VERY easy to tamper with post data.
Please provide an example.
Cheers,
tedd
--
---
http://sperling.com
At 4/7/2007 03:10 AM, Stut wrote:
The difference between get and post is not what you *can* do, it's
what you *should* do.
Get, as the name implies, should be used when retrieving a page. The
URL, including the query string, should contain info needed to
retrieve the right page. No
On Apr 7, 2007, at 9:26 AM, tedd wrote:
At 9:11 PM -0400 4/6/07, Robert Cummings wrote:
On Fri, 2007-04-06 at 20:44 -0400, Mike Shanley wrote:
With POST, everything stays hidden, mostly untamperable, and
Bullshit. It is VERY easy to tamper with post data.
Please provide an example.
On Sat, 2007-04-07 at 10:26 -0400, tedd wrote:
At 9:11 PM -0400 4/6/07, Robert Cummings wrote:
On Fri, 2007-04-06 at 20:44 -0400, Mike Shanley wrote:
With POST, everything stays hidden, mostly untamperable, and
Bullshit. It is VERY easy to tamper with post data.
Please provide an
My Peeps,
I only know of one reason to submit a form as POST and that is because
you can submit more data in one shot.
What other reasons are there?
Chris.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
barophobia wrote:
My Peeps,
I only know of one reason to submit a form as POST and that is because
you can submit more data in one shot.
What other reasons are there?
upload a file?
not have bag of cruft in the url/addressbar?
because POST and GET are semantically different ...
POST
Chris,
When you submit via GET, all the info shows up in the URL, so people can
tamper with it however they like. Also, people can bookmark it as well.
With POST, everything stays hidden, mostly untamperable, and
unbookmarkable. POST might sound clearly better, but unless it's
important
On Fri, 2007-04-06 at 20:44 -0400, Mike Shanley wrote:
Chris,
When you submit via GET, all the info shows up in the URL, so people can
tamper with it however they like. Also, people can bookmark it as well.
Quite true.
With POST, everything stays hidden, mostly untamperable, and
barophobia wrote:
I only know of one reason to submit a form as POST and that is because
you can submit more data in one shot.
At 4/6/2007 05:44 PM, Mike Shanley wrote:
When you submit via GET, all the info shows up in the URL, so people
can tamper with it however they like. Also, people
18 matches
Mail list logo
