How well is Foundation-based projects working in load balanced environments?

[jonascarlbaum]

sessionState etc. is not a good option for load balanced environments.
What components in the current state of Foundation is dependent on sessionState?

We are currently very close to deployment of a Foundation-based project and are experience problems only in load balanced environments (and reverse proxy, Nginx). We are currently suspecting sessionState for our odd behaviors when working on custom error pages etc. (we have replaced Geta/404handler with a custom handler).

Is there more considerations needed to be taken when putting a Foundation-based project in a load balanced environment?

I would like to just turn sessionState to Off but don't know if there is any known huge implications other than what can be read here?

[codeiscool23]

Hi! Out of the box we use the InProc Session-State Mode. You can find that setting here. If you are interested in different Session-State modes or want to disable it entirely please take a look at this documentation.

[jonascarlbaum]

Well, we have turned it off, but my question is, what components/functions in Foundation rely on session state?

What functionality in the out-of-the-box solution would we expect to have issues with!?

Is it only captcha in Forms? We don’t use that one. Anything else?

We want to ensure that nothing outside our own code (that is safe) relies on session state, and therefore we thought that there is something in Foundation still needing it, since you have it configured. I thought Forms no longer needs session state(?).

I just thought it would be great if you could inform if there’s something in Foundation, some external dependency etc. that needs session state.