Ben Taussig

For now, we're focusing on backporting this to v1.12.x. We're hesitant about backporting this further, as it is a new feature and would require a pretty hairy and potentially unstable...

Backport to v1.12.x is resolved with the release of [v1.12.22](https://github.com/solo-io/solo-projects/releases/tag/v1.12.22)

I have just moved this issue to blocked. Some context: - A community user had put up this PR with the intention of resolving the issue: https://github.com/solo-io/gloo/pull/9294 - Per [Jenny's...

After reviewing [this slack thread](https://solo-io-corp.slack.com/archives/G01EERAK3KJ/p1712064353242949), I believe that: - This issue seems to describe a slightly different bug from the one the community user was experiencing - The community PR...

Some clarification: The error is not related to an HTTP 302 redirect response. `[json.exception.type_error.302] type must be string, but is null` is the error that `nlohmann/json`, returns when a user...

## Kickoff Agenda - Issue details to clarify - What client(s) have been affected by this issue? - What AWS auth scheme do they use? - Are they able to...

# Evaluating lambda filter's interactions with 302 response codes I created a lambda to return a "302" ```py import json def lambda_handler(event, context): return { 'statusCode': 302, 'body': json.dumps('Hello from...

I was able to reproduce with the following lambda: ``` import json def lambda_handler(event, context): return { 'multiValueHeaders': { 'foo': [ 'bar', None ] } } ``` The error occurs...

## Design/Implementation Plan ### Overview - The primary concern here is whether this functionality should be implemented as an Inja callback or if we are better off leveraging the transformation...

Update: I have a nearly ready-for-review PR up here: https://github.com/solo-io/envoy-gloo/pull/301 As discussed in that PR's description, there are a couple of things I need to evaluate before this is ready...