When calling an API that includes cache expires, it appears chrome-rest-client
honors this. Even after clearing Chrome's cache, chrome-rest-client continued
to return a cached version.
Upon inspection of outgoing requests using Fiddler, after the initial request
was placed by chrome-rest-client, no additional outgoing requests were
observed.
Is there a way to configure chrome-rest-client to ignore cache headers and
always perform the request?
Original issue reported on code.google.com by rick.moe...@gmail.com on 7 Aug 2013 at 10:52
Original issue reported on code.google.com by
rick.moe...@gmail.com
on 7 Aug 2013 at 10:52