Skip to content

document the direct-response feature#436

Merged
mattklein123 merged 3 commits intoenvoyproxy:masterfrom
brian-pane:direct-response-doc
Jan 26, 2018
Merged

document the direct-response feature#436
mattklein123 merged 3 commits intoenvoyproxy:masterfrom
brian-pane:direct-response-doc

Conversation

@brian-pane
Copy link
Copy Markdown
Contributor

envoyproxy/envoy issue: 2315

Signed-off-by: Brian Pane bpane@pinterest.com

envoyproxy/envoy issue: [2315](envoyproxy/envoy#2315)

Signed-off-by: Brian Pane <bpane@pinterest.com>
Copy link
Copy Markdown
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

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

Thank you. Small nit, also can you see why doc build is failing?

level.
* :ref:`Path <config_http_conn_man_route_table_route_path_redirect>`/:ref:`host
<config_http_conn_man_route_table_route_host_redirect>` redirection at the route level.
* :ref:`Direct HTTP responses <envoy_api_field_route.Route.direct_response_action>`,
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

nit: incomplete sentence.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

That's intentional, to match the style of the rest of the items in the list.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It reads a little weird to me TBH, but not a big deal.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I rephrased this item in the latest commit to this PR. Does the new wording work better?

…s work

Signed-off-by: Brian Pane <bpane@pinterest.com>
Copy link
Copy Markdown
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

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

LGTM, small optional nit/suggestion.

can specify the response body inline or specify the pathname of a file containing the
body. If the Route configuration specifies a file pathname, Envoy will read the file
upon configuration load and cache the contents. Regardless of whether the body is
provided inline or in a file, the body length must be less than or equal to 4KB.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

nit: I might put the 4KB limitation inside an explicit .. attention:: markup with a small explanation of why.

Signed-off-by: Brian Pane <bpane@pinterest.com>
Copy link
Copy Markdown
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

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

sweet, thanks

@mattklein123 mattklein123 merged commit 9582b4c into envoyproxy:master Jan 26, 2018
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.

2 participants