Differing URLs can cause a 502 Bad Gateway error, when the following is true:

• You are using WebDAV as your transfer method
• The GLOBAL-SITE Controller knows the server by one name, but the server knows itself by another name. This could happen when you are using a NAT through a BIG-IP or other load balancer (where the GLOBAL-SITE Controller and the subscriber are not both behind the BIG-IP)

To find the mismatched URLs, look in the subscriber's logs. You can access IIS logs through the IIS manager, httpd logs are in /var/log, and GLOBAL-SITE agent logs are in \Program Files\F5\GLOBAL-SITE Agent\logs.

Once you know the mismatched URLs, you can fix the problem on the subscriber by aliasing the unknown IP address to the known one. To do this, edit the httpd.conf file for the WebDAV agent, and then, depending on your type of web server, use one of the following procedures:

For the WebDAV agent

Edit the httpd.conf file (\Program Files\f5 networks\global-siteagent\conf\httpd.conf) by adding:

<VirtualHost server_hostname>
ServerName server_hostname
ServerAlias unknown_server_address
</VirtualHost>

For Apache web servers (and most UNIX machines)

Edit the httpd.conf file (typically /etc/httpd.conf or /var/httpd/httpd.conf) by adding:

<VirtualHost server_hostname>
ServerName server_hostname
ServerAlias unknown_server_address
</VirtualHost>

For IIS web servers

1. On the site that is using WebDAV, right click and select Properties.
   The Web Site Properties tabbed dialog box opens.
2. On the Web Site tab, click the Advanced button.
3. Follow the product documentation to add the unknown_server_id as a multiple identity in the Multiple identities for this Web Site table.