Hi Steve,
|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.
No, I don't think so. I believe that the above is the same matter.
I agree with you that the .NET has specified the 'advanced' cacheing
mechanism on the server side. Though, I guess that the .NET also uses
the paramters for caching what is specified in the HTTP/1.1 spec to
implement the behavior.
[A column form MSDN];
<http://msdn.microsoft.com/library/en-us/dnaspnet/html/asp03282002.asp>
[HTTP/1.1 specification: RFC 2616];
<http://www.w3.org/Protocols/rfc2616/rfc2616.txt>
- The following sestions are important descriptions;
9.5 POST
13.1.1 Cache Correctness
13.1.3 Cache-control Mechanisms
14.9 Cache-Control
Please note that the parameter is necessary for not only 'client side'
but also 'server side'. In addition, I'd like to suggest that the key
word; 'server side' includes other network devices such as proxy, front
-end web server (for the target SOAP server), and so on.
|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.
Hmm ..., it's too hard work for me. :)
I'd like to propose that this issue should be discussed with
the matter of the asynchronous API. Because of this functionality
will be mostly required in case of async comm. I can post it as a
bug, but I'm not sure whether I'll be able to provide a good work.
Best Regards,
Toshi (Toshiyuki Kimura) <[EMAIL PROTECTED]>
R&D Headquarters
NTT DATA Corporation
-----Original Message-----
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2003 2:08 AM
To: [EMAIL PROTECTED]
Subject: Re: Caching
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
