Task/test and fixes

Mmmm... by introducing this change we have lost the coverage for the case where the modification has actually taken effect. If we are going to test the component with cache activated, we should add another test that waits for the cache to be refreshed (I suppose that behavior can be configured) and then checks whether the request can go on or not. If we don't do that, considering that the cache is a non-functional requirement, I would prefer the old test and a default configuration for the cache of 0ms refresh. What do you think?