xianghai2
xianghai2
That's expected behavior, refer to https://docs.konghq.com/hub/kong-inc/proxy-cache/#cache-control. "the behavior of no-cache is simplified to exclude the entity from being cached entirely"
@khaled4vokalz You may prepare a PR and verify it. thanks.
Hi @TGeb-EV , Could you provide more details about your custom plugin? thank you. And I could not reproduce this, it looks like that Kong 3.7.1 code base works smoothly...
Hi @TGeb-EV , Thanks for more information. And still I could not reproduce it with PUT to update the resource, what I did as following: 1> Update the resource with...
Per my local setup, the behavior of Kong and upstream service do really conform to HTTP standards. According to following text from rfc9110, it looks like that either "2xx" or...
back to this. Hi @TGeb-EV, which phase/function was your plugin implemented for? for me, it looks like that my plugin of the access phase or reponse funtion has no such...
Hi @TGeb-EV , that's probably due to the ETag conformance behavior of response phase plugin or cache. And your upstream test service(index.js) may want to be something like following to...
Let's close this as the dissussoin was done. thanks.
Recommend to use latest version of Kong or Kong-EE.
Recommend to use Kong version 3.8. And check if it's an existing issue: https://docs.konghq.com/hub/kong-inc/cors/changelog/ CC: @randmonkey