Using Restlet 2.1RC6 on Apache Tomcat 6.0.32. I've observed the following behavior:
Web browsers sometimes send an "If-modified-since" header along with their POST requests. (1) Restlet in that case tries to call the @Get handler of the resource before calling the @Post handler, in our case resulting in a 405 / METHOD_NOT_ALLOWED, since our resource in question only has a @Post handler, and no @Get handler (2). While this might be unusual or even non-standard, I'm trying to understand the point of calling the (possibly rather expensive) @Get handler at all before the @Post handler. Is this on purpose? And if so, can this behavior be disabled? (1): I had this with a page that uses XmlHttpRequests to upload multiple image files on an older Safari version (4.1.3); it seems that the second and subsequent POSTs set the header, while the first doesn't. (2): We can work around the problem by implementing a dummy @Get handler which returns an EmptyRepresentation. -- Stefan Deitmer ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3003192
