ARRAffinity cookie is sent with a request and the response is setting it to a different ARRAffinity value

Collin Stevens 1 Reputation point
2020-03-11T15:45:55.493+00:00

I'm seeing requests go through an ASE with an ARRAffinity cookie set and receiving a set-cookie header in the response with a different ARRAffinity value.

I have attached a sample request/response.

ES1pAncU0AAaavJ

Azure Web Apps
Azure Web Apps
A feature of Azure App Service used to create and deploy scalable, mission-critical web apps.
4,320 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Grmacjon-MSFT 8,756 Reputation points Microsoft Employee
    2020-03-26T00:42:25.66+00:00

    Hi Collin,

    Thanks for your patience.

    Looks like something was stripping the header or modifying it prior to reaching the app. A FREB trace (if this is Windows) would probably be helpful in identifying if the cookie is reaching the app service. You will need to modify your web .config with the following entry.

    Add path is where you can specify a specific page to reduce the number of FREB logs created for example

    Failure definitions has to be set since by default when you enable FREB logging it captures status codes > 399.

     <?xml version=”1.0″ encoding=”utf-8″ ?>  
            <configuration>  
                <system.web>  
                </system.web>  
                <system.webServer>  
        <tracing>  
        <traceFailedRequests>  
        <remove path="*" />  
        <add path="*">  
        <traceAreas>  
        <add provider="ASP" verbosity="Verbose" />  
        <add provider="ASPNET" areas="Infrastructure,Module,Page,AppServices" verbosity="Verbose" />  
        <add provider="ISAPI Extension" verbosity="Verbose" />  
        <add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,  
        Cache,RequestNotifications,Module,FastCGI"  
        verbosity="Verbose" />  
        </traceAreas>  
        <failureDefinitions statusCodes="200" />  
        </add>  
        </traceFailedRequests>  
        </tracing>  
            </system.webServer>  
        </configuration>  
    

    6021-ll-2.png

    Please let us know if you have further questions

    No comments