On our system, go to edge rule , and press add rule button.
Hostname is your domain name. Match Location is url path. the defined path , system supports regular expression.
Writing down, hostname field and match location. The system will check match location using PCRE regex expression. when clicked config, it will show settings for this rule. After changing any settings is only need click save button.
This function, it will add customer header on response or request base on url. So you can add many custom headers on the same url, only need click plus button to generate new column and write to new custom headers.
Request header is mlytics' WAF sent headers to client's origin server. For instance , we could setup header name is "company" and header value is " mlytics". On origin server side , client will get header "company" from mlytics' WAF to make sure this requests coming from mlytics.
response header is mlytics' WAF via CDN to client. For example , it is a lot of CORS problems on browsers due to the response header without " Access-Control-Allow-Origin: * ". On mlytics platform , user could setup response header name " Access-Control-Allow-Origin " , response header value " * " to resolve this problem.