-
Notifications
You must be signed in to change notification settings - Fork 17
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
Akamai token validation & rewrite command #13
Comments
It makes sense to me that it behaves as you describe, since nginx's rewrite phase runs before the access phase. Don't think there's much that can be done about it (while technically it may be possible to change the module to run in rewrite phase, that sounds wrong...)
|
we already tried to use the $uri (adding a config parameter set with $uri; parameter is added as complex value type) ;-)... But when we dump the uri received by akamai module, we see the one changed by rewrite....the problem is the one you explained me before (...nginx's rewrite phase runs before the access phase...). my rewrite is like this: I'm not practice about map, please could you help me to set up it correcly? input uri is: ^(./)(././)(./././)(.)(/HLS/)(..m3u8)(.*) map $uri $new { Thanks |
I'm not sure we're on the same page, my second suggestion was for adding a feature that will enable you to choose what is the uri that should be matched against the token's acl. This is not a feature that currently exists, but can be added. |
trying to do this can it be done? |
I don't understand what you are asking. |
Hi,
we tried to use akamai validate module and rewrite the input request with a different one.
We want to execute the rewrite only if the akamai check works fine.
Is it possible? If not, could you suggest a workaround?
here is the configuration example:
location ~ "(my_path)(..m3u8)(.)" {
akamai_token_validate on;
akamai_token_validate_key xxxxx;
akamai_token_validate_param_name hdnea;
rewrite ^(my_path)(..m3u8)(.) /local_path/master.m3u8 break;
}
We noticed that:
-the akamai module is runned only if the break is used in the rewrite command.
With last & redirect it seems that akamai module is not triggered.
-the request uri used by akamai module is the one changed by the rewrite command.
This cause a fault in the akamai check (acl is not compliance...of course).
Thanks for your support.
The text was updated successfully, but these errors were encountered: