Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Zuul post retry on 503

See original GitHub issue

We have a service that returns 503 responses when some dependencies are not available. We are observing that in this situation zuul retry one time.

The problem is that the request is a POST with json body and the first time the body is correctly sent, but when zuul retries, the body is sent empty and it results in a bad request to the client. We are in Angel.SR3 but the response is the same with SR6

{
  "result": {
    "code": 400,
    "info": "Bad Request"
  },
  "errors": [
    {
      "code": "requestBodyInvalid",
      "description": "request body is invalid"
    }
  ]
}

Any idea of how to retry with body?? it seems a serius bug to me

Thanks in advance!!

Issue Analytics

State:
Created 8 years ago
Reactions:1
Comments:15 (7 by maintainers)

Top GitHub Comments

2reactions

ryanjbaxtercommented, Nov 7, 2017

I dont see why not. @spencergibb do you see any reason why we can’t backport this?

1reaction

ryanjbaxtercommented, Aug 3, 2017

@doernbrackandre its not on our radar at the moment, but if you would like to submit a PR with the necessary changes that would be great!

Top Results From Across the Web

zuul (without eureka) - always ends up in "Forwarding error"

Configure retry for Zuul. Extend ErrorFilter and provide custom logic to return 404 or 503 status code. Some of the approaches to deal...

Add central retry handling for github requests · dc42084913 - zuul ...

zuul - The Gatekeeper, or a project gating system. ... We've reached the max retries so let the caller handle thr 503. self.log.error('GET...

Retrying HTTP Requests In Spring Cloud Netflix - Ryan Baxter

Setting zuul. retryable to true or false will control whether all or none of the proxied requests will be retried. By default it...

Retrying Failed Requests with Spring Cloud Netflix Ribbon

We're going to retry a failed request when the client service receives a 503 (service unavailable) or 408 (request timeout) response code.

Timeouts and Retries In Spring Cloud Gateway

I have also highlighted the most important parts of the logs. After several failed retry attempts the delay between subsequent attempts has been ......