makeRequest() sending data as a POST affects client-side caching of the returned HTTP response.
This is server-side caching (HttpCache), which depends not on the method of the call to /gadgets/makeRequest itself, but on the method of the outgoing HTTP request from the Shindig server to the third-party server. If it's POST, it won't be cached, whatever other headers are sent. If it's GET, it would be. On Fri, Mar 20, 2009 at 9:39 AM, Paul Lindner <plind...@hi5.com> wrote: > Sounds like a good idea to me. IIRC makeRequest sends data as a POST, so > we may ot see actual caching occur depending on the browser... > > > > On Mar 19, 2009, at 6:15 PM, Adam Winer wrote: > > The existing code for /gadgets/proxy calls HttpRequest.setCacheTtl() >> with the value in the "refresh" parameter. Louis's new >> "HttpRequestHandler" code does so as well. >> >> The existing code for /gadgets/makeRequest does not. >> >> Any possible reason not to fix /gadgets/makeRequest? >> >> -- Adam >> > >
