Resource activeRefresh behave as a very short cache, even if ketting use the NeverCache implementation

[hugothomas]

Hello,

We are using Prefer header.

Our server is configured to return hal-forms.
On a prefer: return=minimal request, a partial representation is returned (only the _links and the _templates), otherwise the full representation (_links _templates _embedded) will be returned.

My ketting is using the NeverCache implementation.

By doing this :

await Promise.all([
    resource.get({headers: {'Prefer': 'return=minimal'}}),
    resource.followAll('item')
]);

I'm expecting to get two HTTP responses,

• for the first call :

{
  "_links": {
    "self": {
      "href": "selfLink"
    }
  },
  "_templates": {
    "default": {
      "method": "post",
      "properties": []
    }
  }
}

• for the second one :

{
  "_embedded": {
    "item": [
      {
        "name": "toto",
        "_links": {
          "self": {
            "href": "selfLink"
          }
        }
      },
      {
        "name": "titi",
        "_links": {
          "self": {
            "href": "selfLink"
          }
        }
      }
    ]
  },
  "_links": {
    "self": {
      "href": "selfLink"
    }
  },
  "_templates": {
    "default": {
      "method": "post",
      "properties": []
    }
  }
}

But i'm only receiving the first response, only once. The second call isn't performed.

By doing two distinct calls :

await resource.get({headers: {'Prefer': 'return=minimal'}});
await resource.followAll('item');

I'm getting two distinct responses as expected.

According to my research, my issue is caused by Resource.activeRefresh

I'm suggesting to :

• remove activeRefresh behavior. Because by returning a Promise we will not have concurrency problems (maybe I'm missing something).

OR

• add a parameter in the Ketting configuration to bypass the activeRefresh behavior.