Hi, i'm moving my Classic Asp applications to a session-less mode, using a database sessions manager.
<div>In a normal asp session state, a user can make only 1 request at a time, it means that, till the request hasn't been fullfilled, the user won't be able to make another request or open another page on the same session. With this database manager session i noticed that this isn't a limit anymore, while a request is executing, the user can open another tab and continue navigating while the other request is running in the background.However, i don't feel comfy to know that a user could be able to launch infinite requests, since many of them are really resource-consuming.
I tried to use IP ADDRESS AND DOMAIN restrictions to set a maximum of 3 connections per IP, but i had to remove it because some of my users works from inside a LAN, using the same IP, so IIS is not able to make a difference between a single user trying to reload a page multiple times and many users operating within the same network.
Can you suggest me something to solve this problem?</div>