Besides using our platform out of the box, utilizing the tools we offer you by default, there's also a set of options you can deviate from. One of those options is setting up a reverse proxy. Let's take a look at that.
What is a reverse proxy?
So first off, what does a reverse proxy mean? And what does it do?
Because reverse proxies aren't a technique developed by ourselves, but a standard in the technical landscape, we'll look at the description offered by Nginx:
" A proxy server is a go‑between or intermediary server that forwards requests for content from multiple clients to different servers across the Internet. A reverse proxy server is a type of proxy server that typically sits behind the firewall in a private network and directs client requests to the appropriate backend server. A reverse proxy provides an additional level of abstraction and control to ensure the smooth flow of network traffic between clients and servers. "
If you want to read more, go ahead and click the link above. For now, we'll take a look at the technical aspects of it.
Setting up a reverse proxy
The part you started reading this article for! It's not really hard to do, but it does require a bit of technical experience. Also, it's something we do not offer a standard tool for, as it's something you'll have to configure on 'your side'.
You can configure the reverse proxy for your 'Back office' application (
*.bettyblocks.com), your 'frontend' application using endpoints (
*.bettywebblocks.com) and your Pages app, built in the Page Builder (
betty.app). This is done easily through your preferred DNS management tool of the reverse proxy
All you need to do is include the Host header containing your app domain.
The Host request header specifies the host and port number of the server to which the request is being sent.
More information about this can be found on MDN Web Docs/Headers/Host