Cloudflare one - Gateway Forward ( English )
Chapitres
Transcription
Cloudflare 1 Gateway Forward is an innovation from Cloudflare that allows you like very fine control on the request. Let me show you an example. So here I have an employee and that employee wants to access this website, httpbean.org. That employee is connected to the closest Cloudflare data center and his internet traffic goes through Cloudflare. That way Cloudflare protects his internet connection. As an administrator, I put some specific firewall policy for that website or for a specific category of website. So here in that case, I have a firewall policy that says httpbean.org. I can either allow, block, or isolate. Isolate means running the website in an isolated browser on the Cloudflare side to avoid the user to download something from that website or to copy-paste. But here, I selected allo and the user goes to the website update. But now, what if I want to, for example, intercept the traffic here that goes to httpbean and, for example, display a specific warning message or change headers or inspect the traffic more deeply, something like this? Historically, it was not possible to do so. But now, we have a new action on the firewall policy called forward. So forward will forward the request to a serverless function based on Cloudflare workers, which is our serverless platform. And you can send the traffic to serverless function that you control, and you can alter the traffic, inject headers, show warning, anything for the traffic that goes to a specific destination. And because this function, this code is completely serverless, you don't have to manage the scale or the security of this. Everything is managed by Cloudflare. So let me show you another example. So same example, but kind of like in a small demo. So the user goes to httpbean, then there is a firewall policy for that domain specifically, then the rule is forward. So we forward the traffic and with a Cloudflare worker, a serverless function, we decided to display a message warning the user that he is accessing a specific website. So here, I could, for example, ask the user to pass a quiz or test before accessing that page. Once this is done, then he accesses the website. But here, the logic you can put on the Cloudflare workers and the code is up to you and sky is the limit. So in the dashboard, I create a HTTP policy. Here, I select the domains, so domain, HTTP bean, I can select everything. And the action, I select here forward. Okay. And then I select my code, my serverless function, getaway forward warning. I activate this. When the user goes on Google, I type the name of the website and click on the link. Then I show a warning sign. Okay. And here I can do quiz, whatever I want. And then the user accesses the website, everything is logged. So this was Cloudflare one, getaway forward. I hope that helped. See you. Bye.