spring-cloud / spring-cloud/spring-cloud-netflix
Eureka discovery client cannot handle 404 responses with a body
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5k
- Forks
- 2.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 10
Description
Our Eureka server is a plain Boot app so it sends 404s with a nice informative body. Unfortunately the client is not expecting that (as described in #978). We could try and get it fixed in the client, but there might be a workaround in the server as well, if it were to start sending empty error responses to /eureka/apps/**.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the behavior described in #978 and trace how Eureka handles 404 responses with bodies for /eureka/apps/**. Compare the possible client-side handling with the server-side empty-response workaround; done means one agreed approach is specified and the affected 404 behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100