-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[request] Edge Caching #412
Comments
Related to #411 |
Can you clarify what you are requesting? https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching A shared cache inside of Kong or ability to set Cache-Control headers by API to enable private browser cache? |
Since edge-caching is available in the enterprise edition, and this issue deals with where the request comes from (which Kong doesn't deal with, but the infrastructure in front of Kong does) I think there is nothing more we can do here. Can we close this? |
Do we have any update on Edge Caching support in Kong? Since cache plugins will take care of retrieving the data, but How it will take care of getting responses from the nearest kong node as per the client location, to minimize the latency. As of now We use static website hosting on S3 for my Single Page Application (SPA Web App), so I can use CloudFront as well to serve the static files on time. So the same thing, how I can achieve w.r.t Kong? |
unless you do something very specialized, it is not really possible. Usually when a Kong node is hit, you're already in a datacenter somewhere. Kong sits close to the backends. For geo/ip based routing you'd typically use a CDN in front of Kong |
This can be safely closed. |
* test(rpm): test that our rpm's are signed * Update test/tests/01-package/run.sh Co-authored-by: Danny Sauer <danny.sauer@konghq.com> Co-authored-by: Danny Sauer <danny.sauer@konghq.com>
Supports the local caching of requests to closest geographical location, to improve response times for the client.
example:
Kong machine is in Paris and NY. Client is in Paris. Kong will route and cache the request/response from Kong Paris only, to minimize network latency.
The text was updated successfully, but these errors were encountered: