+1 to Dennis' response.

The difference between GET and POST is the method by which the variables are sent. GET uses the query string portion of the URL, so they are visible to the browser operator (the same person conceptually holding the credit card). So hiding it there merely gives a perception of security.

The real security issue is - POST or GET - sending data over the network via plain http - where people you don't even know can read it, and not with a browser. You're using https to transmit credit card numbers, right?

Al

On 7/28/2014 4:21 PM, Halo Maps wrote:

>>  They wanted to do this because they want to send credit card numbers

>> (and other sensitive stuff) and GET is not as secure as POST for this.

>> (I agree with this, by the way.)

 

Get or POST unless it’s encrypted both have the same security standing.  One is just more visible  to the user  than the other.

 

Dennis Powers

UXB Internet - A website Design and Hosting Company

P.O. Box 6028, Wolcott, CT 06716 - T:203-879-2844

W: http://www.uxbinternet.com

W: http://www.ctbusinesslist.com

 

--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en

---
You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en

---
You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to