-
Notifications
You must be signed in to change notification settings - Fork 94
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
Added ApiController to Ocelot Gateway, but gets 404 when requesting it #277
Comments
I've been investigating this the whole day and it seems that either Ocelot or MMLib.SwaggerForOcelot is obstructing the default Routing of ASP.NET I've tried adding custom routes to the Routes config that should point directly to the static files, MvcController or ApiController ... and all of them result in a 90seconds timout and 404 or 503 ..
|
Suggestions tried - didnt work and this |
If you do not add a QoS section, QoS will not be used, however Ocelot will default to a 90 seconds timeout on all downstream requests. https://ocelot.readthedocs.io/en/latest/features/qualityofservice.html |
This might only be a configuration issue..
I've added an ApiController to my gateway / swagger hub project and enabled GenerateDocsForGatewayItSelf
This now shows my Api:
But when i call it i get a 404
Any ideas why ?
The text was updated successfully, but these errors were encountered: