Teju Nareddy

Thanks for the clarification, your architecture makes sense. I didn't know Cloud Functions had that functionality. Yes, it sounds like you need to keep the connector for egress traffic from...

We confirmed that IPv6 routes are not configured by serverless VPC connector. We may consider switching ESPv2 to default to IPv4 only if more users run into this issue.

Ok, we will change the default to IPv4 for the next release. Thanks

We also have a security flag called `--envoy_connection_buffer_limit_bytes`. I believe the default is 1 MiB. If you follow @qiwzhang's advice and deploy ESPv2 with `--enable_debug`, we should see some logs....

@sascha this is a different issue. We have limits configured on the maximum payload size, but you can increase them with the `--envoy_connection_buffer_limit_bytes ` flag: https://cloud.google.com/endpoints/docs/openapi/specify-esp-v2-startup-options#security I believe the default...

> Do you happen to know whether there is any way to change that limit when using Google's API Gateway, which seems to be a fully managed version of ESPv2...

My guess is - these are transient networking errors between the ESPv2 Cloud Run instance and your backend Cloud Function. I am guessing this because all the request execution times...

Hi @dseomn, you can email [email protected] and [email protected] the full log. Yes: - `[http]... request headers complete` is the request headers received from the client. - `[router]... router decoding headers`...

This is interesting. It seems someone else has the same issue: https://github.com/envoyproxy/envoy/issues/13965

You should be able to restrict your nodejs cloud run service so that only ESPv2 can call it. ESPv2 will automatically generate the correct `Authorization` header when connecting to your...