You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! We are using Sentinel in a multi-server environment in AWS, using ELB (Elastic Load Balancer) that acts as a proxy.
Unfortunately, the throttling is using the internal IP. The HTTP header includes the proxy real user address but Sentinel doesn't seem to have any option to get this address instead of the local subnet internal one.
for the record: this only seems to be an issue, if you initialize sentinel before the middlewares are loaded.. i.e. with a static call in a custom service provider
Description
Hi! We are using Sentinel in a multi-server environment in AWS, using ELB (Elastic Load Balancer) that acts as a proxy.
Unfortunately, the throttling is using the internal IP. The HTTP header includes the proxy real user address but Sentinel doesn't seem to have any option to get this address instead of the local subnet internal one.
Do you have any option to get the real user IP ?
Thanks!
Example
Here you can see the local IPs in the throttling table https://snipboard.io/aPz98f.jpg
The text was updated successfully, but these errors were encountered: