Outline

This short checklist explains the requirements for setting up a reverse-proxy so that your Job Board can use a sub-directory of your main site instead of a sub-domain.  For example, this would allow you to use "www.company.com/jobs/" instead of "jobs.company.com".

In order to set up a reverse-proxy, you (the client) must meet the following requirements:

Business requirements

The client must:

1. Have in-house technical expertise to configure, host and maintain their own proxy system, or to implement a solution with a 3rd party provider.
2. Be fully responsible for the uptime, monitoring and maintenance of the proxy system on a permanent basis.
3. Ensure their proxy system is able to cope with the amount of traffic throughput required by their site, and that the system is tolerant of failure.
4. Have a project manager to oversee the implementation of the solution through to launch.
5. Have technical staff able to work out of hours to facilitate the launch.

Technical requirements

The clients reverse-proxy must:

1. Be fully redundant to ensure the solution is highly available.
2. Allow only TLS protocols above TLSv1.1 (SSLv3 and TLSv1.0 must be disabled).
3. Ensure that transit to and from Madgex infrastructure is both:
   1. Secured under HTTPS. Both front-end and back-end must support this.
   2. IP restricted with a whitelist, where the client provides updates as required.
4. Ensure that robots.txt and sitemaps for the top level domain are updated to take account of the Job Board.

Redirects

If a site is launching on a reverse proxy on the client's domain, e.g. www.company.com/careers, then the client should be responsible for setting up all redirects, since the site is on their own domain and redirects will be much easier to setup on the client side rather than passing these to Madgex.