I was expecting a browser fingerprint id in CF header to better check if request is coming from same
I was expecting a browser fingerprint id in CF header to better check if request is coming from same device instead IP address(which can be proxied) or managing a list of disposable email(which is always incomplete).
Anyway, thanks for your suggestions. It seems we'd need to build a layer on our API itself.
Anyway, thanks for your suggestions. It seems we'd need to build a layer on our API itself.
