Skip to content
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

Return 504 on error and other sweeps #6859

Merged
merged 2 commits into from
Feb 15, 2020

Conversation

vagababov
Copy link
Contributor

There exists a more proper response code than 503 to report a timeout
that is 504. QP is a proxy and hence this code is more than suiting for this use case.
We do not guarantee which reponse code is going to be returned in this case (or I could not find).

Other minor nits and bits

/assing @dgerd mattmoor

There exists a more proper response code than 503 to report a timeout
that is 504. QP is a proxy and hence this code is more than suiting for this use case.
We do not guarantee which reponse code is going to be returned in this case (or I could not find).

Other minor nits and bits
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Feb 15, 2020
@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 15, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vagababov

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. area/networking area/test-and-release It flags unit/e2e/conformance/perf test issues for product features labels Feb 15, 2020
@dgerd
Copy link

dgerd commented Feb 15, 2020

Makes sense to me after looking at the RFC https://tools.ietf.org/html/rfc7231#section-6.6.5

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 15, 2020
@knative-prow-robot knative-prow-robot merged commit c0a45e0 into knative:master Feb 15, 2020
@vagababov vagababov deleted the 20200214-return504 branch June 23, 2020 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/networking area/test-and-release It flags unit/e2e/conformance/perf test issues for product features cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants