Set content-type in router_check_tool#10183
Set content-type in router_check_tool#10183kb000 wants to merge 23 commits intoenvoyproxy:masterfrom
Conversation
f011156 to
f823749
Compare
|
cc. @LisaLudique |
0a8dfb4 to
35c9de5
Compare
Signed-off-by: Kevin Burek <kburek@lyft.com>
35c9de5 to
7ffc27a
Compare
Signed-off-by: Kevin Burek <kburek@lyft.com>
Signed-off-by: Kevin Burek <kburek@lyft.com>
7ffc27a to
550376e
Compare
70db9a9 to
a2963b2
Compare
|
/retest |
|
🔨 rebuilding |
mattklein123
left a comment
There was a problem hiding this comment.
Thanks, LGTM w/ 1 question. Nice work!
/wait-any
| "response_header_fields": [ | ||
| { | ||
| "key": "content-type", | ||
| "value": "" |
There was a problem hiding this comment.
Is this goal here to test for absence? It would be a much stronger test if we had an explicit way of testing for this?
There was a problem hiding this comment.
Yes the goal is to test for absence of the content-type header.
Looking at https://tools.ietf.org/html/rfc7230#section-3.2.6, it is possible for field values to be implicitly empty strings (whitespace (trimmed) + CRLF), or explicitly double-quoted empty strings.
It would additionally be stronger from a human readable perspective to be able to say, for instance:
validate:
response_header_fields:
- key: content-type
absent: true
There was a problem hiding this comment.
Let's please just fix this now. Sorry I should have commented on this in @LisaLudique's last PR, but since we just switched the proto to split request/response headers for matching, we should use the HeaderMatcher proto that we already have which makes this type of matching easily possible. Thank you!
There was a problem hiding this comment.
I don't like the scope creep, but ok.
What's the policy on proto changes? Do I need to rename the fields and reserve the old field numbers or am I ok to change it inline because there wasn't a version cut in between?
There was a problem hiding this comment.
We are being a bit loose on this tool, so I think it's OK to just change it since we just changed it already within the last week. I would talk to @LisaLudique about it.
|
@kb000 thanks for working on this. One small comment about using header match. Additionally, please do not force push as it makes reviews more difficult. Just add commits and merge master. Thank you! /wait |
envoyproxy#10168) Signed-off-by: Lisa Lu <lisalu@lyft.com> Signed-off-by: Kevin Burek <kburek@lyft.com>
Signed-off-by: Kevin Burek <kburek@lyft.com>
Signed-off-by: Kevin Burek <kburek@lyft.com>
Signed-off-by: Kevin Burek <kburek@lyft.com>
Signed-off-by: Kevin Burek <kburek@lyft.com>
Signed-off-by: Kevin Burek <kburek@lyft.com>
Signed-off-by: Kevin Burek <kburek@lyft.com>
Signed-off-by: Kevin Burek <kburek@lyft.com>
|
Merge commits and the signoff tool have completely destroyed this branch. I'll create a new PR on monday. |
Description:
Set the content-type header in router_check_tool to better match what the real router does.
Risk Level: Low
Testing: Modified existing test, added negative test.
Docs Changes: None
Release Notes: None
Fixes: #10072