-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Ocelot with Consul, 404 Not Found #1487
Comments
Please try the following method which takes me 4 hours to fix it.
|
@heyruyn23 Does the error appear at the first request or in any? |
Hi @johha86 , I have the same problem, got error on any request. I'm using Ocelot v18 (last one). Any ideea? |
Hi! Thanks for your interest in Ocelot! |
…ements and fix errors (#1670) * fixing some issues in poll consul: - Timer is not thread safe, avoiding usage of it - No Ressources are returned for first call - Using a providers pool, instead of creating a new provider instance * line endings * adding some test cases * Using a lock instead of SemaphoreSlim * Improve code readability * CA2211: Non-constant fields should not be visible * Use IOcelotLogger to remove warnings & messages of static code analysis (aka IDE0052) * Fix errors with unit tests discovery. Remove legacy life hacks of discovering tests on .NET Core * Update unit tests * Also refactoring the kubernetes provider factory (like consul and eureka) * shorten references... * const before... * Some minor fixes, using Equals Ordinal ignore case and a string constant for provider type definition instead of string litterals. Fixing usings. * waiting a bit longer then? * @RaynaldM code review * renaming PollKubernetes to PollKube * ... odd... * ... very odd, we have an issue with configuration update duration... * IDE0002: Name can be simplified * All tests passing locally, hopefully it works online * just a bit of cleanup * Some missing braces and commas * Update servicediscovery.rst: Review and update "Consul" section --------- Co-authored-by: Guillaume Gnaegi <[email protected]> Co-authored-by: raman-m <[email protected]>
Hello, I am very new to Microservice architecture, and I am stuck at this problem for a week.
I really appreciate your help in advance..!
Expected Behavior / New Feature
I am trying to use Ocelot with Consul.
I am not using docker, I am running consul in windows cli.
I have three projects in one solution,
Actual Behavior / Motivation for New Feature
API is running successfully, the service is registered in consul.
But when I tried to call the API from the consul, I get '404 Not Found'.
I think the whatever routing setting in ocelot.json is not working properly... I don't know why..
Steps to Reproduce the Problem
In API Gateway Project
In my Common Library
In my ContactService Project
Specifications
The text was updated successfully, but these errors were encountered: