Persistent cookie in FORTIADC for a Content Routing

[ljramos]

FortiADC 

Our developers have implemented an "auto-save" feature to a web application. using a javaScript function, whenever there is a change in the value of the fields, we write the values to the Cookie. This works as expected when we connect to the website directly to either of the two individual weblogic bypassing the ADC. But when we go thru the ADC, is not working.We don't know the cause, but the condition is that the page keeps refreshing causing all the fields to get cleared. From the logs I see that the Request from the same session is going to a different server. Is there something to check to debug this behavior? 

[Jean-Philippe_P]

Hello Luis Ramos, 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

Thanks, 

[Jean-Philippe_P]

Hello,

We are still looking for an answer to your question.

We will come back to you ASAP.

Thanks,

[Jean-Philippe_P]

Hello again,

I found this solution. Can you tell me if it helps, please?

To address the issue of session persistence when using FortiADC, follow these steps:

1. Check Persistence Configuration: Ensure that the FortiADC is configured to maintain session persistence. This can be done using cookies or the server's IP address. Verify that the persistence method is correctly set up in the FortiADC configuration.
   
   
2. Cookie Injection: Confirm that FortiADC is correctly injecting cookies into the response data. The client's browser should present this cookie back to FortiADC to maintain the session with the same server.
   
   
3. Fallback Persistence: If the primary persistence method (e.g., cookies) fails, ensure that a fallback persistence method is configured. This could be based on the source IP address or another method.
   
   
4. Session Timeout: Check the session timeout settings on FortiADC and the web servers. Ensure that they are aligned to prevent premature session termination.
   
   
5. Logs and Monitoring: Review FortiADC logs for any errors or warnings related to session persistence. This can provide insights into why requests are being directed to different servers.
   
   
6. Network Conditions: Evaluate network conditions and ensure there are no issues causing the session to be interrupted or redirected.

By ensuring that session persistence is correctly configured and monitored, you should be able to resolve the issue of requests being directed to different servers.

[filiaks1]

In addition to @Jean-Philippe_P  TCP multiplexing | FortiADC 7.4.7 | Fortinet Document Library is sometimes useful for cookie persistance expecially if there is another proxy before the ADC.