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
We're currently using ATS v8.1.1.
To support regular expressions in request paths, we've been trying to use the regex_remap plugin in the mapping rules
Rules in the maps.reg file are defined in the following way:
^/.*mp4 $s://$f/$0
We would want to use the signed url plugin, the compression plugin and the allowed methods defined in the .*mp4 mapping rule on requests that match the .*mp4 regex.
For example, requests of the type https://example.com/abc.mp4 should be signed and only get method should be allowed for them.
With the current configurations, https://example.com/abc.mp4 matches the second mapping rule. Post method is allowed for such a request, signed urls are not required and compression isn't supported as well.
Is there a way in which we can enable the use of different remap plugins for different regex rules in the maps.reg file ?
Or is there a simpler workaround for requests to match mapping rules containing regex quantifiers ?
The text was updated successfully, but these errors were encountered:
You can't match on regular expressions like that on the path, so in your case, everything matches the second "map" rule. There's also no way to control different plugins to be run based on the path like that either, the regex_remap plugin does not support that.
I don't know that there's any solution here which would allow you to run the remap plugins conditionally like this.
This issue has been automatically marked as stale because it has not had recent activity. Marking it stale to flag it for further consideration by the community.
We're currently using ATS v8.1.1.
To support regular expressions in request paths, we've been trying to use the regex_remap plugin in the mapping rules
Our remap rules look like this:
Rules in the maps.reg file are defined in the following way:
We would want to use the signed url plugin, the compression plugin and the allowed methods defined in the
.*mp4
mapping rule on requests that match the.*mp4
regex.With the current configurations, https://example.com/abc.mp4 matches the second mapping rule. Post method is allowed for such a request, signed urls are not required and compression isn't supported as well.
Is there a way in which we can enable the use of different remap plugins for different regex rules in the maps.reg file ?
Or is there a simpler workaround for requests to match mapping rules containing regex quantifiers ?
The text was updated successfully, but these errors were encountered: