Toshiyuki Kimura wrote: > Hi Narayanan and Steve, > > [Steve Loughran] wrote in the 'Re: axis and caching'; > | Axis does not specify caching on the results of a POSTed SOAP request, > |because POST requests are not cacheable or idempotent, according to the > |HTTP spec. > > But I'd like to notify 'the HTTP spec.' is only mentioned 'HTTP/1.0'. > If an axis user are using 'HTTP/1.1' as the transport layer and he want > to configure the response as 'cacheable', the response message should be > cacheable. > > Can you make a follow-up for this matter, Steve ? If you need, I can > help you to post it as a bug for POST-1.1.
I think the original poster actually wanted server-side caching, the way .NET does; this is fairly different from what you are talking of, which is setting a lifetime on the validity of responses. if you want to add expires: headers to posts, feel free to come up with a good mechanism to do so, and submit it as usual. -Steve
