The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 |
From: Michael Peterman <mich...@bluesteel.org>
Date: Mon, 22 Oct 2012 23:57:55 -0700 (PDT)
Local: Tues, Oct 23 2012 2:57 am
Subject: Re: [api-craft] Some REST API Best Practice Questions
The fields you listed look like query parameters to me so I think the right thing is to put them in the URL. Why? Well caching a GET request like that is normally done using the origin URL if you craft your response differently based on something other than the URL an intermediate cache could serve the wrong data.
Michael.
on Monday, October 22, 2012 5:53:27 AM UTC-7, KootVanHeerden wrote:
> Thanks. :)
> So, would the correct thing to do for GET and DELETE then be to "sweep it behind the ?" as suggested in the Web API standards document on APIGEE? And for POST and UPDATE sending the data via JSON would be correct? You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||