router: update all http filters to get per filter config by the http filter config name at first (#22002)

Signed-off-by: wbpcode <wangbaiping@corp.netease.com>

Mirrored from https://github.com/envoyproxy/envoy @ 0986bb6d49fbd35e20e567aec0e7d614c9d24663

envoy/config/route/v3/route_components.proto

@@ -145,11 +145,15 @@ message VirtualHost {
   // Indicates that the virtual host has a CORS policy.
   CorsPolicy cors = 8;
 
-  // The per_filter_config field can be used to provide virtual host-specific
-  // configurations for filters. The key should match the filter name, such as
-  // *envoy.filters.http.buffer* for the HTTP buffer filter. Use of this field is filter
-  // specific; see the :ref:`HTTP filter documentation <config_http_filters>`
-  // for if and how it is utilized.
+  // The per_filter_config field can be used to provide virtual host-specific configurations for filters.
+  // The key should match the :ref:`filter config name
+  // <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpFilter.name>`.
+  // The canonical filter name (e.g., *envoy.filters.http.buffer* for the HTTP buffer filter) can also
+  // be used for the backwards compatibility. If there is no entry referred by the filter config name, the
+  // entry referred by the canonical filter name will be provided to the filters as fallback.
+  //
+  // Use of this field is filter specific;
+  // see the :ref:`HTTP filter documentation <config_http_filters>` for if and how it is utilized.
   // [#comment: An entry's value may be wrapped in a
   // :ref:`FilterConfig<envoy_v3_api_msg_config.route.v3.FilterConfig>`
   // message to specify additional options.]
@@ -269,11 +273,15 @@ message Route {
   // Decorator for the matched route.
   Decorator decorator = 5;
 
-  // The typed_per_filter_config field can be used to provide route-specific
-  // configurations for filters. The key should match the filter name, such as
-  // *envoy.filters.http.buffer* for the HTTP buffer filter. Use of this field is filter
-  // specific; see the :ref:`HTTP filter documentation <config_http_filters>` for
-  // if and how it is utilized.
+  // The per_filter_config field can be used to provide route-specific configurations for filters.
+  // The key should match the :ref:`filter config name
+  // <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpFilter.name>`.
+  // The canonical filter name (e.g., *envoy.filters.http.buffer* for the HTTP buffer filter) can also
+  // be used for the backwards compatibility. If there is no entry referred by the filter config name, the
+  // entry referred by the canonical filter name will be provided to the filters as fallback.
+  //
+  // Use of this field is filter specific;
+  // see the :ref:`HTTP filter documentation <config_http_filters>` for if and how it is utilized.
   // [#comment: An entry's value may be wrapped in a
   // :ref:`FilterConfig<envoy_v3_api_msg_config.route.v3.FilterConfig>`
   // message to specify additional options.]
@@ -423,11 +431,16 @@ message WeightedCluster {
       items {string {well_known_regex: HTTP_HEADER_NAME strict: false}}
     }];
 
-    // The per_filter_config field can be used to provide weighted cluster-specific
-    // configurations for filters. The key should match the filter name, such as
-    // *envoy.filters.http.buffer* for the HTTP buffer filter. Use of this field is filter
-    // specific; see the :ref:`HTTP filter documentation <config_http_filters>`
-    // for if and how it is utilized.
+    // The per_filter_config field can be used to provide weighted cluster-specific configurations
+    // for filters.
+    // The key should match the :ref:`filter config name
+    // <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpFilter.name>`.
+    // The canonical filter name (e.g., *envoy.filters.http.buffer* for the HTTP buffer filter) can also
+    // be used for the backwards compatibility. If there is no entry referred by the filter config name, the
+    // entry referred by the canonical filter name will be provided to the filters as fallback.
+    //
+    // Use of this field is filter specific;
+    // see the :ref:`HTTP filter documentation <config_http_filters>` for if and how it is utilized.
     // [#comment: An entry's value may be wrapped in a
     // :ref:`FilterConfig<envoy_v3_api_msg_config.route.v3.FilterConfig>`
     // message to specify additional options.]