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

docs(retries) document the retries setting #445

Merged
merged 1 commit into from
Jul 13, 2017
Merged

docs(retries) document the retries setting #445

merged 1 commit into from
Jul 13, 2017

Conversation

Tieske
Copy link
Member

@Tieske Tieske commented Jun 28, 2017

note: this also has to go to the 0.11 branch

#### 4. Response
#### 4. Errors & retries

Whenever an error occurs during proxying Kong will use the underlying Nginx
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whenever an error occurs while proxying, Kong will use the underlying Nginx retries to pass the request onto the next upstream.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

See the [configuration reference][configuration-reference] for more details.


[Back to TOC](#table-of-contents)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Back to Table of Contents

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not changing this as this is used all over this document

#### 4. Errors & retries

Whenever an error occurs during while proxying, Kong will use the underlying
Nginx [retries][ngx-http-proxy-retries] to pass the request onto the next
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"underlying Nginx mechanism"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"on to", not "onto"


There are two configurable elements here:

1. The number of retries. This can be configured per API using the `retries`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"The number of retries." is a sentance fragment. consider refactoring this to be a complete sentence

server, passing a request to it, or reading the response header.

The second option is based on Nginx's directive
[proxy_next_upstream][proxy_next_upstream]. This option is not directly
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Nginx's proxy_next_upstream directive"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants