Skip to main content

Return to Answer

Added more detail
Source Link
chus
chus
  • 1.7k
  • 16
  • 27

This document W3C documentexplains explains the use of HTTP GET and POST.

I think it is an authoritative source.

The summary is (section 1.3 of the document):

  • Use GET if the interaction is more like a question (i.e., it is a safe operation such as a query, read operation, or lookup).
  • Use POST if:
  • The interaction is more like an order, or
  • The interaction changes the state of the resource in a way that the user would perceive (e.g., a subscription to a service), or
  • The user be held accountable for the results of the interaction.

This document explains the use of HTTP GET and POST.

I think it is an authoritative source.

The summary is (section 1.3 of the document):

  • Use GET if the interaction is more like a question (i.e., it is a safe operation such as a query, read operation, or lookup).
  • Use POST if:
  • The interaction is more like an order, or
  • The interaction changes the state of the resource in a way that the user would perceive (e.g., a subscription to a service), or
  • The user be held accountable for the results of the interaction.

This W3C document explains the use of HTTP GET and POST.

I think it is an authoritative source.

The summary is (section 1.3 of the document):

  • Use GET if the interaction is more like a question (i.e., it is a safe operation such as a query, read operation, or lookup).
  • Use POST if:
  • The interaction is more like an order, or
  • The interaction changes the state of the resource in a way that the user would perceive (e.g., a subscription to a service), or
  • The user be held accountable for the results of the interaction.
Changed your post visibility.No it looks like professional
Source Link
edit approved Aug 17, 2017 at 16:57
Priyantha
edit approved Aug 17, 2017 at 16:57
Priyantha
  • 5.1k
  • 6
  • 30
  • 46

This document explainsdocument explains the use of HTTP GET and POST.

http://www.w3.org/2001/tag/doc/whenToUseGet.html

I think it is an authoritative source.

The summary is (section 1.3 of the document):

  • Use GET if the interaction is more like a question (i.e., it is a safe operation such as a query, read operation, or lookup).
  • Use POST if:
  • The interaction is more like an order, or
  • The interaction changes the state of the resource in a way that the user would perceive (e.g., a subscription to a service), or
  • The user be held accountable for the results of the interaction.

This document explains the use of HTTP GET and POST.

http://www.w3.org/2001/tag/doc/whenToUseGet.html

I think it is an authoritative source.

The summary is (section 1.3 of the document):

  • Use GET if the interaction is more like a question (i.e., it is a safe operation such as a query, read operation, or lookup).
  • Use POST if:
  • The interaction is more like an order, or
  • The interaction changes the state of the resource in a way that the user would perceive (e.g., a subscription to a service), or
  • The user be held accountable for the results of the interaction.

This document explains the use of HTTP GET and POST.

I think it is an authoritative source.

The summary is (section 1.3 of the document):

  • Use GET if the interaction is more like a question (i.e., it is a safe operation such as a query, read operation, or lookup).
  • Use POST if:
  • The interaction is more like an order, or
  • The interaction changes the state of the resource in a way that the user would perceive (e.g., a subscription to a service), or
  • The user be held accountable for the results of the interaction.
Improve formatting
Source Link
chus
chus
  • 1.7k
  • 16
  • 27

This document explains the use of HTTP GET and POST.

http://www.w3.org/2001/tag/doc/whenToUseGet.html

I think it is an authoritative source.

The summary is (section 1.3 of the document):

  • Use GET if the interaction is more like a question (i.e., it is a safe operation such as a query, read operation, or lookup).
  • Use POST if:
  • The interaction is more like an order, or
  • The interaction changes the state of the resource in a way that the user would perceive (e.g., a subscription to a service), or
  • The user be held accountable for the results of the interaction.
  • Use GET if the interaction is more like a question (i.e., it is a safe operation such as a query, read operation, or lookup).
  • Use POST if:
  • The interaction is more like an order, or
  • The interaction changes the state of the resource in a way that the user would perceive (e.g., a subscription to a service), or
  • The user be held accountable for the results of the interaction.

This document explains the use of HTTP GET and POST.

http://www.w3.org/2001/tag/doc/whenToUseGet.html

I think it is an authoritative source.

The summary is (section 1.3 of the document):

  • Use GET if the interaction is more like a question (i.e., it is a safe operation such as a query, read operation, or lookup).
  • Use POST if:
  • The interaction is more like an order, or
  • The interaction changes the state of the resource in a way that the user would perceive (e.g., a subscription to a service), or
  • The user be held accountable for the results of the interaction.

This document explains the use of HTTP GET and POST.

http://www.w3.org/2001/tag/doc/whenToUseGet.html

I think it is an authoritative source.

The summary is (section 1.3 of the document):

  • Use GET if the interaction is more like a question (i.e., it is a safe operation such as a query, read operation, or lookup).
  • Use POST if:
  • The interaction is more like an order, or
  • The interaction changes the state of the resource in a way that the user would perceive (e.g., a subscription to a service), or
  • The user be held accountable for the results of the interaction.
Source Link
chus
chus
  • 1.7k
  • 16
  • 27