|
|
|
|
![]() ![]() |
Mar 30 2005, 04:58 PM
Post
#1
|
|
|
Advanced Member Group: Members Posts: 112 Joined: 29-September 04 From: sweden Member No.: 926 |
Hi
Once opon the time I did use an simple formail witout any script. I can't exactly remember how I did done. But something with post and then my email adress. Does any remember this poor solution??? Thanks Cheers! Jens |
|
|
|
Mar 30 2005, 06:00 PM
Post
#2
|
|
|
PsYcheDeLiC dR3aMeR Group: Admin Posts: 2,242 Joined: 29-January 05 From: Nakorn Chaisri, Thailand Member No.: 2,411 myCENTs:84.36 |
Yaah I surely do - I've mailed myself so many form feedback in this ultra uncouth way
Here it goes: <form action="mailto:you@youremail.com" method="post"> |
|
|
|
Mar 30 2005, 07:48 PM
Post
#3
|
|
|
Techno-Necromancer Group: Members Posts: 1,018 Joined: 13-January 05 From: The Net Member No.: 2,127 |
Follow up question: with the "action = mailto" form I haved used the get method instead of post in the past. With a mailto form, what is the difference between these two methods?
|
|
|
|
Apr 1 2005, 07:03 AM
Post
#4
|
|
|
PsYcheDeLiC dR3aMeR Group: Admin Posts: 2,242 Joined: 29-January 05 From: Nakorn Chaisri, Thailand Member No.: 2,411 myCENTs:84.36 |
No, as far as I know, it's the POST method that you should use with mailto:.
Read this: QUOTE If the processing of a form is idempotent (i.e. it has no lasting observable effect on the state of the world), then the form method should be GET. Many database searches have no visible side-effects and make ideal applications of query forms. - - If the service associated with the processing of a form has side effects (for example, modification of a database or subscription to a service), the method should be POST. Source: HTML 2.0 Specification - Form Submission Section Follow it up with the definition of idempotent: QUOTE Methods can also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N > 0 identical requests is the same as for a single request. Source: RFC2616 The difference between "GET" and "POST" is that the former means "form data is to be encoded (by a browser) into a URL" while the latter means that the form data will be put in the message body. So mailing the form would require POST while GET would encode the whole form as arguements to the URL that form loads after Submit it hit. However, it is recommended that you use the "GET" method when the form processing is "idempotent" only. In short, "GET" is for just getting (retrieving) data whereas "POST" may involve anything, like storing or updating data, or ordering a product, or sending E-mail. Hope this helps |
|
|
|
Apr 2 2005, 02:53 AM
Post
#5
|
|
|
Techno-Necromancer Group: Members Posts: 1,018 Joined: 13-January 05 From: The Net Member No.: 2,127 |
QUOTE The difference between "GET" and "POST" is that the former means "form data is to be encoded (by a browser) into a URL" while the latter means that the form data will be put in the message body. I thought it was the other way around, thanks for letting me know (I just tested it to make sure you were right, no wonder I've always used POST for logins). |
|
|
|
Mar 21 2006, 04:54 PM
Post
#6
|
|
|
Member [ Level 1 ] Group: Members Posts: 35 Joined: 20-March 06 From: Karachi Member No.: 12,138 |
hmmm ...
the mailto Function is not too good ..... Well if u dont wanna use the Scripting urself ... Than why dont u use some Remotely Hosted Scripts .... U can try Black Fire Networks .. Here u can find a CGI Based Form-Mail ... the good thing is that they dont even place Ads on ur Website **** All Appreciations and Criticisms are welcome **** Regards: Samya Khalid |
|
|
|
![]() ![]() |
Similar Topics
| Topics | Topics | |
|---|---|---|
|
|
|
|
Lo-Fi Version | Time is now: 2nd December 2008 - 09:30 PM |