For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Bart_Mollemans_'s avatar
Bart_Mollemans_
Icon for Nimbostratus rankNimbostratus
Aug 20, 2015

iAPPS - SHAAS 2010 - Cookie language identification?

Hello, Since this is my first post/question/anything here... :) Thank you all 4 DevCentral!! I having some issues in the deployment of the new Shaas iApp and am hoping there is a simple fix to it, you could point me to...

 

We have an existing Shaas server cluster currently using NLB... yes I know hence our need to have F5 intervene :) NLB is gone, The F5 is setup, the iApp is deployed and all is working well. Except a very visible feature; namely the fact that for every session now every user has to indicate his/her preferred language each time. :( before a first time user was posed the question by Shaas server (language A or language B) a cookie was send to the client and all is well. For all the following sessions...

 

Now after IApp deployment everyone on opening the sites has to indicate their language... EACH TIME. Because the cookie persistence implemented by F5 IApp inserts their own cookie and doesn't even consider the cookie offered by the servers... I know that re-writing the Shaaap app is a possibility but development is of the opinion: it worked before and should work now!

 

Many thanks for any help you could offer.

 

4 Replies

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    Hi Bart, I'm not familiar with this application. Can you point me to the iApp/deployment guide you used to configure BIG-IP?

     

    thanks

     

  • Mike,

     

    Thank you for your feedback! The application is Sharepoint 2010. SHAAS is Microsoft talk for "Sharepoint As A Service"

     

    Thanks.

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    I've deployed SharePoint many times and never run into this issue. The default F5 cookie persistence shouldn't have any effect on a setting like this. Assuming the client is being correctly persisted (by whatever means) to the initial server they logged on to, and is reliably sending the cookie that tells SharePoint about the language selection, then it's not a persistence issue.

     

    What is the name of the SharePoint cookie you identified as being responsible for this setting?

     

  • Mike,

     

    Again thank you for your interest. Meanwhile; I have found the solution. the issue was that I was looking in the wrong place. the language selection was a custom 'feature' in java for one of the main fqdn's of the SharePoint cluster. They created their own cookie based on a selection window offered to the user. Now when your persistence method used on F5 ltm is set to cookie insertion, the cookie formed by the little in site java-app never get's to play. Solution: Change the persistence method to cookie-hash all is well :)

     

    Again may thanks and good luck in future F5 endeavors.