[GitHub] [apisix] tokers commented on pull request #3382: chore: the 500 response code in the upstream.lua file was changed to 503 response code

tokers commented on pull request #3382: URL: https://github.com/apache/apisix/pull/3382#issuecomment-764628665 Does the broken compatibility really no matter? This is an automated message from the Apache Git Service. To resp

[GitHub] [apisix] tokers commented on pull request #3382: chore: the 500 response code in the upstream.lua file was changed to 503 response code

tokers commented on pull request #3382: URL: https://github.com/apache/apisix/pull/3382#issuecomment-764690785 You don't know whether people rely on the status code. @Firstsawyou This is an automated message from the Apache

[GitHub] [apisix] tokers commented on pull request #3382: chore: the 500 response code in the upstream.lua file was changed to 503 response code

tokers commented on pull request #3382: URL: https://github.com/apache/apisix/pull/3382#issuecomment-765066584 > > You don't know whether people rely on the status code. @Firstsawyou > > got it, this is something to consider. > But these 500 response codes are inappropriate for use

[GitHub] [apisix] tokers commented on pull request #3382: chore: the 500 response code in the upstream.lua file was changed to 503 response code

tokers commented on pull request #3382: URL: https://github.com/apache/apisix/pull/3382#issuecomment-765078054 So i think this PR can be closed now, just reopen it when necessary. This is an automated message from the Apache

[GitHub] [apisix] tokers commented on pull request #3382: chore: the 500 response code in the upstream.lua file was changed to 503 response code

tokers commented on pull request #3382: URL: https://github.com/apache/apisix/pull/3382#issuecomment-764628665 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and us