Hi,
On Mon, Aug 25, 2014 at 9:42 AM, Udara Liyanage <ud...@wso2.com> wrote: > Hi, > > According to the http spec, response to a POST does not send a response > body. Resource created is set in location header. Client can identify > whether operation is successful by looking at http status code which is 201 > in this case. However there is no hard rule that no response body should be > sent. IMO having http code and body message is duplicating. > In addition there are cases where response body is empty, for instance JMS > message sending. > So the ideal case is to fix Jaggery. If it is not possible only, add a > response message as a work around. > +1 for fixing it in Jaggery. I will send a message in response body as workaround for now, since this issue is a blocker for development. > > Touched, not typed. Erroneous words are a feature, not a typo. > -- Rajkumar Rajaratnam Software Engineer | WSO2, Inc. Mobile +94777568639 | +94783498120
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
