[BUG] After Upgrading AzureAppConfiguration AppInsights receives suddenly status 302 for refresh key checks

[jsquire]

Issue Transfer

This issue has been transferred from the Azure SDK for .NET repository, #42025.

Please be aware that @mpodonyi is the author of the original issue and include them for any questions or replies.

Details

Library name and version

Microsoft.Azure.AppConfiguration.AspNetCore 7.0.0

Describe the bug

After upgrading from Microsoft.Azure.AppConfiguration.AspNetCore V5.1.0 to V7.0.0 and Microsoft.Extensions.Configuration.AzureAppConfiguration V5.1.0 to V7.0.0

I am receiving suddenly Refresh Key Check Warnings of status 304 every 5 seconds (my refresh intervall) inAzure App Insights.

This is flooding my loggings and should not be so.

Expected behavior

No 304 Warnings should be shown in AzureAppInsights for Refresh Key Checks where the when the Sentinel Values hasn't changed

Actual behavior

The 304 Warning for Refreshkey Changes is suddenly appearing in my logs.

Reproduction Steps

The internal call to AppConfiguration Refresh Key is causing returning 304 which is logged. https://[hidden].azconfig.io/kv/%21Trigger?api-version=2023-10-01

Environment

No response

[amerjusupovic]

@mpodonyi This issue looks very similar to another we've gotten linked here. Upgrading our dependency to the newest version of Azure.Data.AppConfiguration is when 304s started showing as failures, and I've reached out to the Application Insights team for support on this issue. If you can also send feedback to Application Insights under the "Help" tab for your resource in the Azure portal, I think it would help them get more context on how this issue arose.

I don't see a way to fix this from our end at the moment, but I hope to find an answer soon.

[amerjusupovic]

Closing this issue and keeping #514 open to track this