task

title

[previously]

  1. ] send form methods 
    1. ] 
  2. ] get
    1. ] default method
    2. ] passes form data(querystring) in url, 
    3. ] use GET for 'safe' actions
    4. ] more usable b/c 
      1. ] cacheable - browsers can cache
      2. ] history - browser can maintain history of pages retrieved with get
      3. ] bookmarkable - 
      4. ] distributable - can share (email, social, etc) links with 
      5. ] hackable - as in you can 'predict' what view/articles/2012, could be changes to view/articles/2013, /2011, etc depending on the sites
    5. * COMMENTer Vincent Robert -I think REST describes it right. GET is only about URIs, it is about getting the representation of a resource identified by a URI. Now some prefer pretty URIs but using query variables is perfectly legal in HTTP.
  3. ] post
    1. ] use post for 'unsafe' actions
    2. ] passes querystring data in body of post (more secure)
    3. ] sends form input 
    4. ] browser must implement repeat WARNING IF resending
    5. ] use for submitting sensitive data, 
    6. ] > length ( vs 4kb) 
    7. * COMMENTer Vincent Robert POST is about processing. It is about sending content to a resource for processing. Again, this resource can have a URI using query variables.

[currently]

  1. ]  

[next]

  1. ] REFERENCE
    1. The Definitive Guide to GET vs POST - Treehouse Blog
Details Photos Edit more

Details

ID: 2890

NAME: CREATE-article-get-vs-post

DESCRIPTION: ] ovu, ] quick reference, ] explain the difference between these HTTP methods BK=> HTTP

START DATE TIME: 2013-10-09 13:16:30

EST DURATION: 01:00:00

END DATE TIME: 2013-10-09 14:16:30

STATUS: In-Process

PRIORITY: -5

OWNER ID: 75

Content Photos Edit more

photos

photos for this task

actions

Agenda Email task SMS task Priorities