I want to allow my users to cache the content of a HTTPS incoming web-hock

[nelson-vendoo]

I have modified the cache-control header on the function but I still am getting a cache-control: no-cache, no-store, must-revalidate from de service

      ...      
      response.setHeader("Content-Type", "application/json");
      response.setHeader("cache-control", "max-age=3600");
      response.setBody(JSON.stringify(result));
      ...

[jsflax]

I'm not entirely sure what the reasoning for this would be, but if you want to change the way we digest responses, you have to supply your own Transport to the StitchClientConfiguration you pass in when you initialise your app client.