# Relaying files > How the Front-end server serves files to clients without direct access to a container. Source: https://docs.capaone.com/capainstaller/the-capainstaller-console/system-administration/what-is-system-administration/services/front-end-service/relaying-files/ Product: CapaInstaller — a separate CapaSystems product; do not apply this page to any other. The Front-end server does not need direct access to a container to serve files to clients. This means that there is no requirement for a management server or distribution server in order to operate a Front-end server. This is particularly useful when you want to deploy a Front-end server to a DMZ. This is done is by letting the Front-end server in the DMZ (Frontend Server 2) relay file requests to another Front-end server (Frontend server 1) on the inside of the DMZ. ![](/attachments/capainstaller/85fedc87-de80-4dbb-87a8-a6b20b1229ca.png) The base agent (Base Agent 2) connects to the Front-end Server on the supplied public port (P2). A redirect in the outer Firewall (2) is made to the public port of the Frontend server 2 (P1). Frontend server 2 in the DMZ operates just like Frontend server 1 on the inside of Firewall 1. It has a connection to the database (S) and makes the same validations and queries as Frontend server 1. The only difference is that queries to files on Frontend server 2 are relayed further to Frontend server 1 which Gets or Puts the files from/to Frontend server 1. To set up this functionality, Frontend server 2 must relay file requests to Frontend server 1. Since there is a firewall between the two, the relay URL must point to P3 in Firewall 1. A redirect in Firewall 1 must then be made to the public port (P1) on Frontend server 1. This is done with the command-line argument; /relayurl=.