envoy: http: gRPC-web filter does not clear the route cache
Title: gRPC-web filter does not clear the route cache
Description:
source/extensions/filters/http/grpc_web/grpc_web_filter.ccchecks if the incoming request is a gRPC-web request and transforms it to gRPC proper. The transformation involves changing the content type toapplication/grpc. Unlike the JSON transcoding filter, gRPC-web one does not however clear the route cache making it harder to route the “upgraded” request the same way one would route a native gRPC request.
Envoy version: master @ 97d259d43a4f9b7c6d798804b4b2c9ffbd2d285d (02/11/2019)
Repro steps: Define a route explicitly matching gRPC traffic:
...
"match": {
"prefix": "/",
"grpc": {}
},
"route": {
"cluster": "lo_svc_grpc",
"max_grpc_timeout": {
"seconds": 0
}
},
{
"match": {
"prefix": "/"
},
"route": {
"cluster": "lo_svc_http",
"timeout": {
"seconds": 60
}
}
}
...
Define the http filters in the following order:
...
"http_filters": [
{
"name": "envoy.grpc_web"
},
{
"name": "envoy.router"
}]
...
Send a gRPC-web request through Envoy
Expected: the request is upgraded to gRPC proper and routed to lo_svc_grpc
Actual: the request is upgraded to gRPC proper and routed to lo_svc_http (the cached route)
Why is this a bug?
- JSON transcoding filter clears the cache and supports such routing - consistency issue.
- The documentation states the filters are executed in order of their definition, since the router was defined as the last one, it should pick up the changes made by the previous filters.
- The routing supports matching on
gRPCrequests and when the gRPC-web request reaches the router, it is agRPCrequest at that point and should be routed as such.
Workaround:
Insert a route matching the initial request on gRPC-web explicitly:
{
"match": {
"prefix": "/",
"headers": [
{
"name": "content-type",
"prefix_match": "application/grpc-web"
}
]
},
"route": {
"cluster": "lo_svc_grpc",
"max_grpc_timeout": {
"seconds": 0
}
}
},
Proposed fix:
decoder_callbacks_->clearRouteCache();
after the line https://github.com/envoyproxy/envoy/blob/master/source/extensions/filters/http/grpc_web/grpc_web_filter.cc#L60
About this issue
- Original URL
- State: open
- Created 5 years ago
- Comments: 18 (18 by maintainers)
Feel free to open an PR as long as requiring header is opt-in thus not breaking existing users. I don’t feel much value as it is a config problem in general, and if you have a proto descriptor defined transcoding clashes with the native HTTP endpoint, you will have your own problem anyway.
Transcoding filter try to match incoming request to proto descriptor but if it doesn’t, it is basically no-op.
For this particular case, IMO we can add a flag into
GrpcRouteMatchOptions, such asinclude_grpc_webso the route will match grpc-web request too before the filter, WDYT?