I am testing a published service from test site <myapp>/rest-doc/<service>/<resource>. It works as expected the first time with a response-code 410, but that apparently triggers the test site to use a cache at the next attempt. Copying and pasting the curl command and calling that using -H “Cache-Control:no-cache” makes sure that the cache is not used. Can we do that somehow from the /rest-doc/ test-site?
Tim van Steenbergen
Are you sure that 410 is the expected response you are looking for? I think the caching is a result of this response code. It would never cache on a 200 or 500 response. I've never seen swagger interfaces where this can be configured in. Try using postman?