AWS Lambda Serialization Handling for Asp.Net Core OutputCache

[tvytrykush]

I am running ASP.NET Core Web API with controllers inside of Lambda via AddAWSLambdaHosting(LambdaEventSource.RestApi) and I also use new IOutputCache feature and use Elasticache Redis to cache responses. What I noticed is that when I run the app within regular hosting environment - the values cached are serialized properly and can be retrieved without any troubles, but values serialized when running in Lambda are terminated with a \x00 (e.g. full value: \x02\xD3\xAF\xD2\x85\xD4\xEE\x90\xEE\x08\x00\xC8\x01\x02;\x012text/plain; charset=utf-8A\x01:Wed, 13 Mar 2024 15:50:05 GMT\x00). I can't figure out if Lambda hosting environment has something to do with this the cache serialization format and how do I control it if yes?

For reference, my caching policy is very simple and looks like this:
`ValueTask IOutputCachePolicy.CacheRequestAsync(OutputCacheContext context, CancellationToken cancellationToken)
{
var attemptOutputCaching = AttemptOutputCaching(context);

    context.EnableOutputCaching = true;
    context.AllowCacheLookup = attemptOutputCaching;
    context.AllowCacheStorage = attemptOutputCaching;
    context.AllowLocking = true;
    context.ResponseExpirationTimeSpan = CacheExpirationPeriod;
    context.CacheVaryByRules.QueryKeys = "*";

    context.Tags.Add(TagPrefix + context.HttpContext.Request.RouteValues["controller"]);
    
    return ValueTask.CompletedTask;
}

private static bool AttemptOutputCaching(OutputCacheContext context)
{
    var request = context.HttpContext.Request;

    return HttpMethods.IsGet(request.Method) || HttpMethods.IsHead(request.Method);
}

`

[ashishdhingra]

This is tracked as part of #1702.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.