feat: PRT - Websocket limited per ip

[ranlavanet]

Description

Closes: #XXXX

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• read the contribution guide
• included the correct type prefix in the PR title, you can find examples of the prefixes below:
• confirmed ! in the type prefix if API or client breaking change
• targeted the main branch
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

[github-actions]

Test Results

2 230 tests  ±0   2 230 ✅ ±0   26m 15s ⏱️ + 1m 0s
  145 suites ±0       0 💤 ±0 
    7 files   ±0       0 ❌ ±0 

Results for commit 3ffb49a. ± Comparison against base commit 1962ab0.

♻️ This comment has been updated with latest results.

[nimrod-teich]

I wouldn't use the IP alone as the unique identifier to map the open sockets (what happens when users behind NAT are sending requests?).
A combination of the real IP (extracted from X-Forwarded-For) and user-agent is adviced.

[omerlavanet]

I wouldn't use the IP alone as the unique identifier to map the open sockets (what happens when users behind NAT are sending requests?). A combination of the real IP (extracted from X-Forwarded-For) and user-agent is adviced.

agreed and i would take it a step further, allow a special header to change the rate, and we force set this header on our nginx, because otherwise you have to manage special rate limits within the consumer

[ranlavanet]

@nimrod-teich , @omerlavanet

I've added a header to rate limit. functionality is quite the same as the flag just here we can control it from ngnix instead of directly in process

Header name:
WebSocketRateLimitHeader = "x-lava-rate-limit"

Example use:
-H "x-lava-rate-limit: 10" (will result in rate limit of 10 requests per second)

[omerlavanet]

if currentRequestsPerSecondLoad is very low and the header is given the user is banned, i don't get it

[omerlavanet]

you add then immediately decrease, and not when the connection is down, no other writes to the active connections, this will always be true

[omerlavanet]

we said we will do this based on dappId, ip and user agent