Skip to content
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

Could Kong just proxy request but not wait for response from proxied servers? #2387

Closed
ShinEDL opened this issue Apr 13, 2017 · 8 comments
Closed

Comments

@ShinEDL
Copy link

ShinEDL commented Apr 13, 2017

What I need just proxy request, but wait for response make QPS slow.
Looking forward your answer ! thank you !

@Tieske
Copy link
Member

Tieske commented Apr 13, 2017

how would that deal with an error?

@p0pr0ck5
Copy link
Contributor

One could write a plugin hat makes an asynchronous HTTP call upstream, ignores the response, and sends a synthetic response downstream. But I doubt any feature like this will ever make it into Kong core ;)

@ShinEDL
Copy link
Author

ShinEDL commented Apr 14, 2017

@Tieske It does't matter, because our business don't need response. haha...

@ShinEDL
Copy link
Author

ShinEDL commented Apr 14, 2017

@p0pr0ck5 If it could make into Kong core, that would be so great.

@thibaultcha
Copy link
Member

thibaultcha commented Apr 14, 2017

@ShinEDL No more plugin will make it into Kong core, sorry! In fact, the current plugins will actually be taken outside of the core, and the later will stay lean.

We will bundle a set of default plugins in the release archive instead :) See #2355 for some context.

@ShinEDL
Copy link
Author

ShinEDL commented Apr 14, 2017

@thibaultcha Thank for your response.
What I think is if this feature could be implement by Kong? It is useful for some kind of business, such as time-limited sales on second.
sorry for my poor English...

@bungle
Copy link
Member

bungle commented Apr 14, 2017

This could possibly make into (upcoming) a plugins API. Outside of core it is just about requiring lua-resty-http and running it in timer. It already has the proxy function built-in.

@p0pr0ck5
Copy link
Contributor

@ShinEDL kong's core functionality is to use nginx's built-in proxying mechanism to proxy the request. as mentioned, short-circuiting this is certainly doable with a plugin, but it doesn't belong in a core proxying framework- indeed, this is what plugins are for! :) we provide a reference at https://getkong.org/docs/0.10.x/plugin-development/ for writing, testing, and deploying your own plugins, and we'd love to hear about your experience writing new plugins for your environment via Gitter, the mailing list, etc. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants