Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Throttling for proxy (AWS ELB) #531

Open
rubenvl2 opened this issue Apr 21, 2020 · 4 comments
Open

Throttling for proxy (AWS ELB) #531

rubenvl2 opened this issue Apr 21, 2020 · 4 comments

Comments

@rubenvl2
Copy link

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

@brunogaspar
Copy link
Member

Seems to be a problem within the Symfony Http component as i don't recall we retrieve the ip address in any other way.

@rubenvl2
Copy link
Author

@brunogaspar thanks! will investigate further with symfony/Laravel and if we find anything will post it back here. Thanks! :)

@brunogaspar
Copy link
Member

Sure, sounds good.

I know that there issues with load balancers on Google Cloud App Engine, not sure if it's kinda related with AWS.

@ikkez
Copy link

ikkez commented Sep 7, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants