Skip to content

Adding a configuration option for proxying 100 continue#433

Merged
htuch merged 3 commits intoenvoyproxy:masterfrom
alyssawilk:100-continue
Jan 25, 2018
Merged

Adding a configuration option for proxying 100 continue#433
htuch merged 3 commits intoenvoyproxy:masterfrom
alyssawilk:100-continue

Conversation

@alyssawilk
Copy link
Copy Markdown
Contributor

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
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. Can we not merge until @kyessenov big PR merges?

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
@htuch htuch merged commit e6aa0cf into envoyproxy:master Jan 25, 2018
alyssawilk added a commit to envoyproxy/envoy that referenced this pull request Feb 6, 2018
By default Envoy will still strip Expect: 100-Continue and send the 100 Continue response, but for each HttpConnectionManager configured to proxy_100_continue it will pass the header through and proxy the 100 Continue from upstream.

Risk Level: Medium-High (http connection manager refactor)
Testing: thorough unit tests and integration tests
Docs Changes: envoyproxy/data-plane-api#455
Fixes #2325
[API Changes:] envoyproxy/data-plane-api#433
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