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

Kong fails to process path based routing rquests immediately after adding an API #592

Closed
ahmadnassri opened this issue Oct 5, 2015 · 1 comment

Comments

@ahmadnassri
Copy link
Contributor

  • add an API profile using request_path
  • attempt to make a request to proxy port using the path specified
  • Kong fails to respond with the message API not found with these values
  • after a while (a few seconds) the request seems to go through (seems to be cache related?)

image

@thibaultcha
Copy link
Member

This is the expected behavior until #15 is implemented.

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

2 participants