05-04-2021, 09:18 PM
(This post was last modified: 05-04-2021, 09:23 PM by Alexandre Machado.)
I'm not sure if I understand what exactly you mean by:
"On some servers it happens every time when we try to receive data using an app, and then the app cannot continue."
How are you receiving data? Are you exposing some URL as a content handler or something?
Some context: When the application starts, IntraWeb stores the IP and the hash code of the user agent string (the browser) which initiated the session. At each subsequent request IntraWeb can *optionally* compare the IP and the UA hash with the original ones. If something changed, it can *optionally* raise an exception and drop the session.
What you need to figure out is why the UA is changing between requests? Is it a legit scenario? If so, you should just turn off this feature (ServerController.SecurityOptions.CheckUA) or, if not, why is it happening?
"On some servers it happens every time when we try to receive data using an app, and then the app cannot continue."
How are you receiving data? Are you exposing some URL as a content handler or something?
Some context: When the application starts, IntraWeb stores the IP and the hash code of the user agent string (the browser) which initiated the session. At each subsequent request IntraWeb can *optionally* compare the IP and the UA hash with the original ones. If something changed, it can *optionally* raise an exception and drop the session.
What you need to figure out is why the UA is changing between requests? Is it a legit scenario? If so, you should just turn off this feature (ServerController.SecurityOptions.CheckUA) or, if not, why is it happening?