Hello,

In regards to this, it is possible to have stricter rate limiting on more specific junctions.

using the example above, you could set a policy on https://test.rate.org/junction1 for 100 requests per minute.

Then you can also have a policy on https://test.rate.org/junction1/junction2 that is stricter (50 requests per minute).

In our case we want to have the more general junction (/junction1) to be stricter than the specific url (/junction1/junction2). Is this possible?

We are using wildcards within the policy and would like to have an option within the policy yaml file to exclude one but match all the rest.

So similar, to the original post, but instead of getting stricter on more specific junctions, we want the rate limiting to be more lenient on a specific junction.

Jerry,

WebSEAL will apply the request against all matching rate limiting policies.  This means that if you have a policy on https://test.rate.org/junction1, and another policy for https://test.rate.org/junction1/junction2, any requests for a resource like: 'https://test.rate.org/junction1/junction2/index.html', will have a bucket in both rate limiting policies.   There is no way to tell WebSEAL to ignore a rate limiting policy for certain requests. 

I hope that this helps.

Scott.

Hello,

In regards to this, it is possible to have stricter rate limiting on more specific junctions.

using the example above, you could set a policy on https://test.rate.org/junction1 for 100 requests per minute.

Then you can also have a policy on https://test.rate.org/junction1/junction2 that is stricter (50 requests per minute).

In our case we want to have the more general junction (/junction1) to be stricter than the specific url (/junction1/junction2). Is this possible?

We are using wildcards within the policy and would like to have an option within the policy yaml file to exclude one but match all the rest.

So similar, to the original post, but instead of getting stricter on more specific junctions, we want the rate limiting to be more lenient on a specific junction.

Hi all,

Is this still the situation in IVIA 11.0.0.0?
And if so, is there another way to achieve this within IVIA?

Jerry,

WebSEAL will apply the request against all matching rate limiting policies.  This means that if you have a policy on https://test.rate.org/junction1, and another policy for https://test.rate.org/junction1/junction2, any requests for a resource like: 'https://test.rate.org/junction1/junction2/index.html', will have a bucket in both rate limiting policies.   There is no way to tell WebSEAL to ignore a rate limiting policy for certain requests. 

I hope that this helps.

Scott.

Hello,

In regards to this, it is possible to have stricter rate limiting on more specific junctions.

using the example above, you could set a policy on https://test.rate.org/junction1 for 100 requests per minute.

Then you can also have a policy on https://test.rate.org/junction1/junction2 that is stricter (50 requests per minute).

In our case we want to have the more general junction (/junction1) to be stricter than the specific url (/junction1/junction2). Is this possible?

We are using wildcards within the policy and would like to have an option within the policy yaml file to exclude one but match all the rest.

So similar, to the original post, but instead of getting stricter on more specific junctions, we want the rate limiting to be more lenient on a specific junction.

Hi all,

Is this still the situation in IVIA 11.0.0.0?
And if so, is there another way to achieve this within IVIA?

Jerry,

WebSEAL will apply the request against all matching rate limiting policies.  This means that if you have a policy on https://test.rate.org/junction1, and another policy for https://test.rate.org/junction1/junction2, any requests for a resource like: 'https://test.rate.org/junction1/junction2/index.html', will have a bucket in both rate limiting policies.   There is no way to tell WebSEAL to ignore a rate limiting policy for certain requests. 

I hope that this helps.

Scott.

Hello,

In regards to this, it is possible to have stricter rate limiting on more specific junctions.

using the example above, you could set a policy on https://test.rate.org/junction1 for 100 requests per minute.

Then you can also have a policy on https://test.rate.org/junction1/junction2 that is stricter (50 requests per minute).

In our case we want to have the more general junction (/junction1) to be stricter than the specific url (/junction1/junction2). Is this possible?

We are using wildcards within the policy and would like to have an option within the policy yaml file to exclude one but match all the rest.

So similar, to the original post, but instead of getting stricter on more specific junctions, we want the rate limiting to be more lenient on a specific junction.

Scott,

Can multiple URLs be put in one rate limit rule? For example, should these be divided into two rule files? or can both be put in one?

Can the below all go in one limiting rule? 

# Examples GET, POST

resources:
  - url: "/status-dev/dev/*"
    method:
      - POST

  - url: "/status-dev/test/*"
    method:
      - POST

Hi all,

Is this still the situation in IVIA 11.0.0.0?
And if so, is there another way to achieve this within IVIA?

Jerry,

WebSEAL will apply the request against all matching rate limiting policies.  This means that if you have a policy on https://test.rate.org/junction1, and another policy for https://test.rate.org/junction1/junction2, any requests for a resource like: 'https://test.rate.org/junction1/junction2/index.html', will have a bucket in both rate limiting policies.   There is no way to tell WebSEAL to ignore a rate limiting policy for certain requests. 

I hope that this helps.

Scott.

Hello,

In regards to this, it is possible to have stricter rate limiting on more specific junctions.

using the example above, you could set a policy on https://test.rate.org/junction1 for 100 requests per minute.

Then you can also have a policy on https://test.rate.org/junction1/junction2 that is stricter (50 requests per minute).

In our case we want to have the more general junction (/junction1) to be stricter than the specific url (/junction1/junction2). Is this possible?

We are using wildcards within the policy and would like to have an option within the policy yaml file to exclude one but match all the rest.

So similar, to the original post, but instead of getting stricter on more specific junctions, we want the rate limiting to be more lenient on a specific junction.