# Configuring Pathologic When Going Live

This module [Pathologic](https://www.drupal.org/project/pathologic) is already installed and configured within Varbase. The main purpose of this module is to fix all URLs that should redirect to the production site if it was redirected to the internal contents.

To navigate to the Pathologic configuration page: **Administration \ Configuration \ Content authoring \&#x20;**_**Pathologic configuration**_

There are three type of URL formats:

* **Full URL (http://example.com/foo/bar)**:  This option is best for stopping broken images and links in syndicated content (such as in RSS feeds), but will likely lead to problems if your site is accessible by both HTTP and HTTPS.
* **Protocol relative URL (//example.com/foo/bar)**:  Paths output with the _Protocol relative URL_ option will avoid such problems, but feed readers and other software not using up-to-date standards may be confused by the paths.
* **Path relative to server root (/foo/bar)**:  The _Path relative to server root_ option will avoid problems with sites accessible by both HTTP and HTTPS with no compatibility concerns, but will absolutely not fix broken images and links in syndicated content.

{% hint style="info" %}
We recommend to use the "**Path relative to server root**" option. That so that paths appears relative to your website, and to be actually served from your own domain name.
{% endhint %}

![Pathologic configuration section](https://1551857219-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LMp_PWjEdZQrVE520s3%2F-MLY_nKIGVmXX8ZoOCqb%2F-MLYaiH2JMXOBepJz0BL%2Fimage.png?alt=media\&token=9967e487-6744-4392-859b-3ceb3cb9ef49)

As you have noticed from the above screenshot in the text area field "All base paths for this site", we have inserted the base URLs as example links acting as testing environments and the production environment:

* https://www.example.com/
* http://www.example1.com/&#x20;
* https://dev.example.com/&#x20;
* http://dev.example.com/&#x20;
* https://stg.example.com/
* http://stg.example.com/

We will test this for example let us create new Basic page content and insert text with hyperlinks:

* "Link" is linked to "https://www.example.com/test"
* "Link1" is linked to "https://www.example1.com/test"
* "Link2" is linked to "https://www.example2.com/test"

![Creating new Basic page with linked contents](https://1551857219-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LMp_PWjEdZQrVE520s3%2F-MLZHdA8uhJrWT9yNDN6%2F-MLZMorEMeFhVv9i1aDx%2Fimage.png?alt=media\&token=84c9f8b9-7f5f-4008-927b-88527e0eb3b9)

After we created the Basic page content, let us know how the links are showing on the frontend by using the inspect element (DevTool)

![](https://1551857219-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LMp_PWjEdZQrVE520s3%2F-MLZXOpZ_JVuBnqaRpAe%2F-MLZbA6tZcTy5XnDYft2%2Fimage.png?alt=media\&token=75afce79-030b-4e4d-8f39-b4b2d2fcd186)

As you can see from the screenshot above, notice "Link2" how it is linked and the rest links are being stripped out from the base URL, this is because "https://www.example2.com/" is not listed within the "All base paths for this site" field.
