---
title: Avoiding internal IP disclosure when configuring redirects in HTTP farms
description: "## Redirects Redirects are very useful in HTTP farms for steering the users to certain URLs in specific cases for security (redirecting from HTTP to HTTPS) or just to avoid HTTP 404 not found errors, among other situations. Applying redirects…"
url: "https://www.relianoid.com/resources/knowledge-base/troubleshooting/avoiding-internal-ip-disclosure-when-configuring-redirects-in-http-farms/"
updated: "2023-11-01"
category: Troubleshooting
---

# Avoiding internal IP disclosure when configuring redirects in HTTP farms

## Redirects

Redirects are very useful in HTTP farms for steering the users to certain URLs in specific cases for security (redirecting from HTTP to HTTPS) or just to avoid HTTP 404 not found errors, among other situations. Applying redirects in the load balancer side, will unload the real servers from such tasks and improve network performance.

Having a wrong configuration of redirections could lead in security concerns due to internal disclosure of IP addresses.

## Redirection with IP disclosure

When **Enable Redirect** is set in our HTTP farm service, the field **Redirect URL** is shown. Entering values with IP addresses such as "**https://10.10.10.5/login.html**" or "**https://localhost/login.html**" would lead into an internal IP disclosure like it is shown below.

![](https://www.relianoid.com/wp-content/uploads/2023/11/relianoid_avoid_redirect_internal_ip_disclosure.webp)

## Avoid IP disclosure

The proper way to configure a redirect without internal disclosure is using the full qualified domain in the **Redirect URL** as it is set in the **Virtual Host** field. Please refer to the picture below.

![](https://www.relianoid.com/wp-content/uploads/2023/11/relianoid_correct_redirect_http_farm-1024x877.webp)

### 📄 Download this document in PDF format