Backend Services
Last updated
Last updated
This section defines the Backend Services that Reblaze will protect. In other words, these are the destinations to which Reblaze will send the (legitimate) traffic it receives.
A Service consists of one or more endpoints (defined in the Endpoint List, discussed below). Each Service can receive traffic for multiple web applications, and for multiple resources/locations within each web application.
For a single Service, you can define multiple endpoints. Within them you can:
Enable and configure load balancing, weighting and distributing traffic across your primary endpoints.
Define backups hosts, to which Reblaze will failover your traffic when your primary hosts aren’t available.
Take hosts offline for maintenance by ticking a single box in the interface.
Backend Services are designated to receive traffic for specific destination URLs in Server Groups.
The main window (shown above) lists all currently defined Backend Services.
The administration (addition/deletion/editing/versioning) of these Services follows the conventions described here.
A name for this Service, to be used within the Reblaze interface.
Sometimes an application requires a user to be connected to the same Reblaze instance and backend endpoint throughout the session. Reblaze can ensure that this occurs, and can do so using a variety of methods.
Setting | Behavior |
None | This is the default. Requests will be distributed across the endpoints in a round-robin fashion, according to the Weights assigned to them (described below in the ). |
Auto Cookie | Reblaze will automatically generate a cookie to maintain the session on the same endpoint. |
Custom Cookie | You can provide the name of the cookie that Reblaze will use to track the session, e.g. one generated by an AWS or GCP load balancer. |
IP Hash | Routing will be determined from a hash of the client and destination IP addresses. |
Least Connection | Requests will be sent to the endpoint with the fewest number of connections. |
Information about this Service, for use within the interface.
This configures the communication between Reblaze and the backend.
Option | Value |
Per Request | This is the default mode. Incoming HTTP requests will go over HTTP, and incoming HTTPS requests will go over HTTPS. |
HTTP Always | All communication between Reblaze and the backend will be over HTTP. (This mode should not be used unless Reblaze runs within the same cloud as the backend.) |
HTTPS Always | All communication between Reblaze and the backend will be over HTTPS. |
Port Bridge Mode | Reblaze will use the same port as the incoming request. This is not limited to ports 80 and 443; Reblaze will use whatever port was specified. Note: this mode is not available when more than one host is defined. |
This is a list of one or more endpoints. The settings for each endpoint in the list are as follows.
Attribute | Description |
Host | The name or IP address for each endpoint that Reblaze protects. (Do not enter self-referential values such as 127.0.0.0/8, 0.0.0.0, ::1/128, ::0/128 or “localhost”.) The host can be a normal web server, or it can be a load-balancer. Note that Reblaze also provides load-balancing capabilities in its own right, as discussed below. In Port Bridge Mode, it is possible to specify more than one host, separated by commas (as in the screenshot above). |
HTTP Port | The HTTP port(s) for the server. To add a port, click in the field, and enter the port number into the "Search" field. |
HTTPS Port | The HTTPS port(s) for the server. To add a port, click in the field, and enter the port number into the "Search" field. |
Weight | The relative weight of each server for load-balancing purposes. Reblaze distributes traffic with a round-robin sequence, according to these weights. For example, if two servers are both set to 'weight=1', they will receive equal amounts of traffic. If the first is set to 'weight=3' while the second is set to 'weight=1', the first server will receive three visitors for every single visitor that the second server receives. |
Max Fails | The maximum number of failed communication attempts that are allowed for this server. Once this number of failures occurs, Reblaze will consider the server to be inactive. If other servers are available, Reblaze will failover the traffic to them. If this was the only server available, Reblaze will return an error to the client (either 504 Timeout, or 502 Bad Gateway). |
Fail Timeout | When a server fails, this is the length of time in seconds that Reblaze will wait before trying to send traffic to it again. |
Is Down? | When this box is checked, Reblaze will not attempt to communicate with this server. This allows you to take a server offline for temporary maintenance or some other purpose. |
