ashish b

A few questions here: 1. @ably77 Based on my testing, client-provided headers are not passed to extauth by default. There are some configuration options that allow this however: ``` spec:...

Okay, after some offline discussions, we'd like to confirm what the desired behaviour is for this: 1. if extauth rejects the request, the header should be deleted from requests to...

https://github.com/solo-io/gloo/runs/7452064700?check_suite_focus=true ``` 2022-07-21T15:23:45.1269030Z [Fail] Kube2e: gateway tests with virtual service with a mix of valid and invalid virtual services [BeforeEach] propagates the valid virtual services to envoy 2022-07-21T15:23:45.1273642Z /home/runner/work/gloo/gloo/test/kube2e/gateway/gateway_test.go:660 ```

hit this again here: https://storage.googleapis.com/solo-public-build-logs/logs.html?buildid=1ecbeefc-2bf9-4d56-8173-d6626880f33e ``` Step #10 - "test": Gateway in memory tcp gateway ssl [It] should work with ssl Step #10 - "test": /workspace/gloo/test/e2e/gateway_test.go:696 Step #10 - "test":...

Possibly related issues: https://github.com/solo-io/gloo/pull/8461 https://github.com/solo-io/gloo/pull/8407 In short, we had some issues in how errors were being registered for some of our listeners on hybrid gateways (tcp listeners specifically, I think,...

@asayah We cherry-picked the patch you mentioned in [this comment](https://github.com/solo-io/gloo/issues/9313#issuecomment-2197732372) from upstream envoy into envoy-gloo and it has been released in **OSS** gloo version 1.17.1. Would it be possible for...

We've had a lot of discussion on this in multiple locations, but to summarize where we stand, we merged the patch in Gloo and released it in OSS Gloo 1.17.1....

From user feedback (see [this thread](https://solo-io-corp.slack.com/archives/C04RLT77XTP/p1721944758825839?thread_ts=1721853345.624769&cid=C04RLT77XTP)), it seems that the existing behaviour regarding `Status` is consistent with other observability products, so this fix seems to fit user needs and should...

Since we have successfully backported the patch in question and released it (OSS Gloo 1.17.1 and Gloo-EE 1.17.0), I feel that it's safe to close this issue. The `Status code`...

Current status: known segmentation fault in one of the inja transformer tests: (**EDIT**: this is fixed by https://github.com/solo-io/envoy-gloo/pull/333/commits/0058721f2b7ac8cb71641b75e47c3c7086240e64) ``` user@9b2344d5ee3c:/build/envoy-gloo$ bazel test -c dbg //test/extensions/filters/http/transformation:inja_transformer_replace_test --test_output=errors INFO: Invocation ID: 9f7edd5c-214d-4733-8beb-5b31aedba6a7...