I have an application we want to connect to, but the connection closes after 120 secs of inactivity. The problem is in the timeout of the proxy.
I have used a Rule to increase the timeout when we connect to a website. I have modified the event "Enable Proxy Control", and inside it I have changed the timeout in the field HTTPs, FTP, ICAP to 300 seconds, but it doesn't work. The proxy continues taking the default value (120 secs)
If I change the default value in the global configuration, it works. The timeout for the aplication increases.
Do you have any idea about why the rule doesn't work?
I have checked it and now its correctly applied, i had the web name in the rule and i have changed to public IP Adress, and the rule is matching correctly now. But i still have another problem. The application (CITRIX), at 5 -7 min, freezes when this rule is working so I have to close it.
Do you think that i need to modify another parameter?
Usually Citrix applications will send some sort of keep alive message in order to prevent the connection from going stale. If you increase the timeout as you did above, does this seem increase the time it takes for the app to freeze? For the way you're doing this (using Proxy Control with criteria based on host or dest IP) it's safe to increase the timeout even higher (9999 is as high as you can go).
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.