Hi, Am Dienstag, den 29.04.2008, 13:41 +0200 schrieb Tobias Bocanegra: > > The Location header seems to in fact not be set for a content creation > > request. I agree, that this is a bug in the SlingPostServlet. Could you > > please create an issue for that one ? Thanks. > the location header is only present for redirects, of course.
Not necessairily. It is also to be sent with 201/Created. This is not currently supported. > > > > and there will be another request parameter > > > which allows to override the response code for special case handling > > > like hidden iframes in forms. This parameter could be named > > > sling:post:responseCodeOverride and the value could be the response > > > code that should be used. If the parameter is not present the real > > > response code will be send. > and what do you do if you create and modify and delete several > resources at the same time? what response code do you send? Hmm, you might probably not do this in an Ajax Request anyway, right ? I suppose in Ajax you one operation per request, as is the intention with HTTP anyway. Anyway, the SlingPostServlet prepares for a 201/Created response if the request is identified as a creation request, regardless of any other operations requested. Regards Felix
