Artica Reverse Proxy Edition is designed to protect web services and enforce the security, speed and privacy of your web applications.
It approaches Layer 7 defense.
It use signature-based approaches by delivering security protections and operational improvements
Artica is designed to block new, unknown attacks by default, conducting advanced threat analysis on inbound content to detect and protect infrastructure from attacks.
The Reverse-proxy consists of receiving user requests and transferring them to one or more web servers.
The reverse-proxy is then between the clients and your websites.
With Artica Reverse-Proxy, make sure your website is protected from online threats while enjoying optimum speed.
With this advanced web security solution, you can protect your site against DDoS attacks, SQL injections, XSS attacks and much more.
What's more, this caching technology speeds up the loading of your site, delivering a fast, fluid user experience.
More details on security features in the security dedicated security section to this part.
The reverse-proxy features load balancing capability enabling connections to be transferred to the available web server.
- Setup multiple backends using load-balancing
Configure the load balancing method to efficiently distribute traffic among backend servers, making it an excellent choice for handling high traffic applications, microservices, and distributed architectures.
- The keepalive feature
The keepalive feature plays a crucial role in optimizing the performance and efficiency of network connections between the reverse-proxy and backends servers
- Redirect incoming requests from one port to another
Your virtual server listens on multiple ports, and you need to forward all requests from specific ports to a different one.
- Use specific DNS servers
Using Specific DNS servers in reverse-proxy brings several benefits, especially in dynamic environments where backend services or external resources may change IP addresses frequently
- Use an outgoing interface
This feature allows you to specify the source IP address that the reverse proxy will use when connecting to upstream servers, enabling you to choose which IP to use for outbound connections.
- Accept Proxy Protocol
When using the Artica Reverse Proxy behind a load balancer (such as PulseReverse), the Proxy Protocol allows the load balancer to transmit the original client’s source IP address and port to the backend web servers.
This information is essential, as it enables Artica Reverse Proxy to accurately monitor and log client activity at the proxy level.
¶ Limits and bandwidth
The DoH gateway mode transforms a DNS service that only resolves UDP/TCP requests into a DNS Over HTTPs service.
A PHP website is a Web service that runs on the reverse-proxy server, using a dedicated PHP engine (version 8.3.4) to provide dynamic websites using the PHP language.
Artica Reverse Proxy allows you to easily publish websites composed of static HTML content.
This feature is especially valuable when you need to deliver a website quickly and with minimal system resources. It is ideal for serving lightweight content such as maintenance pages, landing pages, or documentation sites…
- Create a static HTML web site
A static website allows you to serve flat files such as ISO images and Office documents.
It can also render HTML pages but does not include a backend engine for generating dynamic content like a CMS such as WordPress.
- Privileges access to the working directory.
To ensure proper operation, you must upload the files into the designated working directory.
If you're using the SSH service, make sure your user account has the necessary write permissions on this directory.
- Optimizing reverse-proxy for Large File Delivery
Artica is able to automatically tunes the reverse-proxy to efficiently serve large files such as ISO images, software packages, or media content.
- WebDav Access
This feature provides direct access to the working directory, allowing you to upload content to the Artica appliance and generate the web pages you require
Artica's web console listens on a different port, but you can make it available as a traditional website by adding a dedicated reverse-proxy rule.
Caching through the reverse-proxy means you don't need to query your backend server for regularly requested objects, and enables the reverse-proxy to produce web pages even if your backend servers are unavailable.
- The SLA feature
The SLA feature allows you to regularly test your your backend's capabilities...
- Turning to 503 error if system capacity exceeded
This feature monitors memory usage (including swap partition), processor load and average system requests response time of , as well as processor utilization...
- Reverse-proxy backend watchdog
This feature is designed to check the health of protected Web servers and send an alert if they are down or if an issue is discovered.
- Check your reverse configuration
Artica can check access from the machine itself. Two checks take place...
- Turn on debug mode on a website
The verbose mode allows you to discuss with ArticaTech's support team in case of problems encountered on a Web site.
- Search and display real-time requests
Real-time requests monitor section allows you to view and search for user requests to your web services
- Extracting Requests from Reverse-Proxy Legal Logs Storage
By extracting and analyzing request data from reverse-proxy logs, organizations can identify suspicious patterns, detect potential security threats, and mitigate attacks such as DDoS, brute force attempts, or unauthorized access attempts.
This proactive approach strengthens overall cybersecurity posture.
- Grafana and Prometheus
Using Grafana and the Prometheus Exporter allows you to monitor and visualize your Reverse-Proxy metrics in real-time.
This setup is particularly useful for gaining insights into server performance, traffic patterns, and resource utilization
¶ Maintain