Andrew M. Bishop <[EMAIL PROTECTED]> wrote: > Joerg Sommer <[EMAIL PROTECTED]> writes: > >> >> Boinc a tool for searching small green man in outerspace ([EMAIL >> >> PROTECTED]) >> >> sends its data with POSTs to the server. While I'm offline it fills me >> >> the outgoing cache with POST requests. And a request gets everytime a >> >> differnt POST id, which undermine the concept of wwwoffles offline >> >> request/online fetching. >> >> >> >> How can disable caching of POST requests while offline? >> > >> > You cannot disable the POST itself, but you could set the URL that the >> > POST is sent to as 'dont-request = yes' in the OfflineOptions section. >> >> Why does confirm-requests not work? > > The confirm-requests option should work just as well as dont-request. > Are you saying that there is a problem with confirm-requests?
Yes. I set "confirm-requests = yes" (for all) and excluded some URLs. But I could ever make a POST request and it was cached without confirmation. >> > [id of a post request] >> >> But why is the id everytime different? If the id is a hash about the post >> data I get the same result with the same data. This way seti can work >> offline. > > There is a fundamental difference between a GET request and a POST > request that should be taken into account. Even though it is possible > to create an HTML form that uses either type there is a difference. > > [...] > > So to give an example of what it means to be "taking an action other > than retrieval" consider that there was a web shop. > > The URL http://shop.foo/view-product?id=1234 would be the one that > showed you the information about the product (using GET). The URL > http://shop.foo/buy-product using the POST method with the body > contents of 'id=1234' would actually buy one of these products. Ehmm, ok. This example makes it clearer. Then the form I have in mind is misdesigned. I request a table of call by call providers, but I don't take an action like filling a shopping basket. Regards, J�rg. -- Gienger's Law (http://www.bruhaha.de/laws.html): Die Wichtigkeit eines Newspostings im Usenet ist reziprok zur Anzahl der enthaltenenen, kumulierten Ausrufungszeichen.
