> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/connectivity/load-balancer/how-tos/create-a-http-load-balancer/log-visitors-ip-addresses-and-protocol.md).

# Log visitors' IP addresses and protocol

***

In the log files of the web servers—the targets—only the load balancer's IP address is logged by default. This is because the load balancer is the one making requests to the web servers. However, it is possible to retrieve the visitor's IP address, as well as the protocol used, by reading two additional headers in the web server.

The Glesys load balancer adds the headers `X-Forwarded-For` and `X-Forwarded-Proto`.

`X-Forwarded-For` contains the IP address of the visitor, meaning the IP address that made the request to the load balancer.

`X-Forwarded-Proto` contains the protocol used when the visitor made the request to the load balancer. This will be either HTTP or HTTPS.

## Apache2 <a href="#apache2" id="apache2"></a>

In Apache2, add these two headers as custom fields in the `access.log` file by creating a custom *LogFormat*. This is done in the website's configuration file in Apache2, for example: `/etc/apache2/sites-enabled/example.com.conf` for the domain [*example.com*](http://example.com) (on Debian and Ubuntu).

{% code title="example.com.conf" %}

```apache2
<VirtualHost *:80>
    ServerName www.example.com
    ServerAlias example.com
    ServerAdmin webmaster@example.com
    DocumentRoot /var/www/html

    LogFormat "%h %l %u %t %{X-Forwarded-For}i %{X-Forwarded-Proto}i \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" loadbalancer
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log loadbalancer
</VirtualHost>
```

{% endcode %}

The name *loadbalancer* after the `LogFormat` and `CustomLog` lines is a name you assign to the log format. The format is based on the standard *combined* log format in Apache2, but here we have added the new headers after the timestamp. A log entry using this format might look like this:

{% code title="access.log" %}

```
203.0.113.81 - - [14/Nov/2023:18:53:44 +0000] 198.51.100.96 http 
"GET / HTTP/1.1" 200 220 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0)
Gecko/20100101 Firefox/119.0"
```

{% endcode %}

Here, 203.0.113.81 is the IP address of the load balancer. The visitor's IP address is 198.51.100.96. The visitor used HTTP to connect to the load balancer.

## PHP

Typically, you can display the visitor's IP address using PHP with the following snippet.

```php
<?php echo $_SERVER['REMOTE_ADDR']; ?>
```

However, this will only display the IP address of the load balancer, since it's the load balancer that makes the request.&#x20;

To display the visitor's IP address, you need to use the header `X-Forwarded-For` instead. The following PHP snippet will display the IP address of the actual visitor.

```php
<?php echo $_SERVER['HTTP_X_FORWARDED_FOR']; ?>
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.glesys.com/products/connectivity/load-balancer/how-tos/create-a-http-load-balancer/log-visitors-ip-addresses-and-protocol.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.