On 06.12 09:49, Stefan Palme wrote: > "Not cacheable" means, server responses will not be stored in the cache. > But does it also mean, that existing objects in the cache will never be > *used* for POST requests? > After the first "GET /form.html", "form.html" may be stored in the > cache, because this is no POST request. The following "POST /form.html" > may *use* the stored object (and not sending the POST request to the > server). "GET /form.html" is different object than "POST /form.html". they will be handled separately. > I guess this is not the same as what it meant by "POST requests are not > cacheable", because "cachable" means *storing* objects in the cache, > but this scenario describes *using* of stored objects... no, it means both. > May this really happen? Or will objects retrieved by GET requests never > used for POST requests (and vice versa)? that highly depends on those objects. note that objects may be set up cacheable and in such cases they will be cached. -- Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. The early bird may get the worm, but the second mouse gets the cheese.
