Hello Garry, I'm sorry for the delay of my answer. At this moment, we need some to support the EXPECT header (see http://restlet.tigris.org/issues/show_bug.cgi?id=413) which is planned for the 2.0 RC. Some pieces are needed in order to make the Request#onResponse() able to catch such intermediary responses.
Regarding the support S3 scheme, the client side of this scheme is available and is working (via the "crypto" extension). I see that it is based on the Date header (or the current Date). I've fixed the report issue regarding the DATE header. Thus, you will be able to set your own date. Best regards, Thierry Boileau > Hi Thierry, > > Thanks for this response, even if it does make my life more complicated! > > What I'm building is basically a clone of Amazon's S3. On the server side > this has been more or less fine using Restlet -- modulo the issues I've > previously raised re the AuthenticationHelper and support for > Expect/CONTINUE -- but it looks like I'll not be able to build a > Restlet-based client. > > Which makes me ask what the point is of the support for the S3 scheme in > ChallengeResponse? The values in that scheme are dependent on being able > to read and sign actual header values such as Date. > > I read the Javadoc for onContinue and when it said it was called before > the entity was sent I wasn't sure just how literal that was. Not sure > about that use case but for my purposes a callback prior to the dispatch > of the entire request that would allow examination and modification of the > actual request (both headers and entity) to be sent would be really > useful. > > Cheers, > Garry > > > On Thu, 14 Jan 2010, Thierry Boileau wrote: > > >> Hi Garry, >> >> I'm afraid not. This value is set with a "new Date()" value just before >> the header is written... >> >> The "onContinue" was thought to be called before the entity is sent, >> after the headers were written. I say "was", because it has been removed >> since no clear use case emerged. >> >> Best regards, >> Thierry Boileau >> >> >>> Hi, >>> >>> I too hit this problem as I wanted to set a specific value for the Date >>> header. >>> >>> In absence of this ability -- I've seen issue 1001 -- can I get the value >>> of the header client side before the request is sent in any way? I want to >>> set another header based on the date. >>> >>> I thought that setting a Uniform instance as the oncontinue handler of the >>> ClientResource would allow this but the handle() method in Uniform doesn't >>> seem to be called before the request is actually sent? >>> >>> Thanks, >>> Garry >>> >>> ------------------------------------------------------ >>> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2436971 >>> >>> >>> >> ------------------------------------------------------ >> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2437281 >> > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2440023
