404 Error with OpenAPI
See original GitHub issueHi all,
New to fastAPI, and coming from Flask, I’m very impressed by the solution.
But using the OpenAPI documentation/UI, I can see in the logs that I have the following issue each time I extend a resource/API :
INFO: <IP>:57175 - "GET /%5Bobject%20Module%5D HTTP/1.1" 404 Not Found
The API is working, but I get this error in the log.
I’m using v0.63.0, on an ubuntu server (18.04)
Thanks a lot for your support.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:17
- Comments:27 (3 by maintainers)
Top Results From Across the Web
How to specify multiple 404 causes in OpenAPI (Swagger)?
If the client gets a 404 it could either because the delivery ID was not found, or the delivery did not contain any...
Read more >OpenApi 3 (Swagger UI), Spring Boot, Spring Security: 404 ...
antMatchers() rule to your SecurityConfig still has 404 error. I'm using: Spring Boot v2.4.1; Spring Security; OpenApi 3 with swagger-ui ( ...
Read more >Getting error 404 in deployed swagger project - Google Groups
For the 404, it's likely you didn't set your basePath of your application. You received this message because you are subscribed to the...
Read more >404 NotFound while accessing Apis
hello, You have to create a REST resource at /api/banks/1 first; otherwise you ...
Read more >HTTP 404 for swagger-ui - Open API
NET Core Web Application already running with SwaggerFeature plugin : Swagger UI link is visible from /metadata page, and is working as excepted ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Created a pull request with a temporary fix to this (#2656). Thanks @Gatux for linking the issue with the monkey patch.
I also get the samme INFO message in my log