Testing the origin

Sometimes an issue might arise but it is hard to tell whether the problem is on the origin, or an intermediate proxy.


Rather than switching public DNS records and losing the benefits of caching and other performance optimisations from section.io for all users, which can also exacerbate the issue by increasing traffic to the origin, it is beneficial to bypass the section.io platform on your local PC to run tests.

To do so, edit your local HOSTS file to map the site directly to the origin.


We will use www.site.com as an example hostname.

  1.  Determine the IP address of the origin. You might already know this, but if you only have an origin hostname you can obtain the IP by running the following in a command prompt

    nslookup origin.site.com

    The result should look similar to this 



    If multiple IP addresses are returned from the nslookup, pick one.
    Lets say in this case the result was 123.123.123.123


  2. Locate the HOST file on your system.

     Windows:  c:\Windows\system32\drivers\etc\hosts

     Mac:   /etc/hosts

    The above are the default locations, they may be different on your system.


  3. Open the file with your preferred text editor.
    Add an entry into the host file to map the site directly to the origin. eg:

    123.123.123.123 www.site.com


  4. Now go to a browser, in this case Chrome, with dev tools open(ctrl+shift+i). Navigate to the site and look under Network tab and examine the response headers for the HTML document to confirm section.io has been bypassed. 

    If the document was served through section.io, you will see either "via: Squixa" and/or "section-io-id" header. If you do not see either of these headers, you have bypassed section.io.



  5. Now try and reproduce the issue. If the same problem still occurs, then the origin should be the focus of further investigation.
Have more questions? Submit a request

Comments

Powered by Zendesk