Throttling services with IP behind load balancer
up vote
0
down vote
favorite
I am using 3 load-balanced WSO2-ESB5.0.0 instances, I can get clients' IP in the X-Forwarded
header.
I configured a throttling policy which acts based on clients' IP; but since the requests are passing through the load balancer, the client IP is replaced by the load balancer IP.
I can not configure the throttling policy to read from X-Forwarded
header, so I can not apply my throttling policy over the load-balanced ESBs.
I'd rather not to change the load balancer configuration since that is not under my control completely.
wso2 wso2esb
add a comment |
up vote
0
down vote
favorite
I am using 3 load-balanced WSO2-ESB5.0.0 instances, I can get clients' IP in the X-Forwarded
header.
I configured a throttling policy which acts based on clients' IP; but since the requests are passing through the load balancer, the client IP is replaced by the load balancer IP.
I can not configure the throttling policy to read from X-Forwarded
header, so I can not apply my throttling policy over the load-balanced ESBs.
I'd rather not to change the load balancer configuration since that is not under my control completely.
wso2 wso2esb
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using 3 load-balanced WSO2-ESB5.0.0 instances, I can get clients' IP in the X-Forwarded
header.
I configured a throttling policy which acts based on clients' IP; but since the requests are passing through the load balancer, the client IP is replaced by the load balancer IP.
I can not configure the throttling policy to read from X-Forwarded
header, so I can not apply my throttling policy over the load-balanced ESBs.
I'd rather not to change the load balancer configuration since that is not under my control completely.
wso2 wso2esb
I am using 3 load-balanced WSO2-ESB5.0.0 instances, I can get clients' IP in the X-Forwarded
header.
I configured a throttling policy which acts based on clients' IP; but since the requests are passing through the load balancer, the client IP is replaced by the load balancer IP.
I can not configure the throttling policy to read from X-Forwarded
header, so I can not apply my throttling policy over the load-balanced ESBs.
I'd rather not to change the load balancer configuration since that is not under my control completely.
wso2 wso2esb
wso2 wso2esb
asked Nov 19 at 16:08
Reza Ameri
1,29931729
1,29931729
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378580%2fthrottling-services-with-ip-behind-load-balancer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown