You are looking at the HTML representation of the XML format.
HTML is good for debugging, but probably is not suitable for your application.
See complete documentation, or API help for more information.
<?xml version="1.0"?>
<api>
  <query-continue>
    <allpages gapfrom="Thunderbird" />
  </query-continue>
  <query>
    <pages>
      <page pageid="36" ns="0" title="SSL Certificates">
        <revisions>
          <rev xml:space="preserve">== Why use SSL? ==

SSL Certificates, even self signed certificates, allow for secure and encrypted communication between you and the server you are connecting to. If you do not use encryption, you are transmitting&lt;br /&gt;
your information in clear text. In cases of a man-in-the-middle attack this can mean all of your passwords, and private information is easily readable.

= Internet Explorer =

1. Start Internet Explorer running as a user with administrative privileges.&lt;br /&gt;
2. Browse to server computer using the computer name (ignore certificate warnings)&lt;br /&gt;
3. Click the ”Certificate Error” text in the top of the screen and select ”View certificates”&lt;br /&gt;
4. In the Certificate dialog, click Install Certificate -&gt; Next&lt;br /&gt;
5. Select Place all certificates in the following store -&gt; Browse&lt;br /&gt;
6. Check Show Physical Stores check box&lt;br /&gt;
7. Select Trusted Root Certificate Authorities – Local Computer&lt;br /&gt;
8. Click OK – Next – Finish – OK&lt;br /&gt;
9. Restart Internet Explorer&lt;br /&gt;

= Firefox =

1. Start Firefox as a user with administrative privileges.&lt;br /&gt;
2. Open Tools and to to Options&lt;br /&gt;
3. Click the Advanced Tab, then Encryption Sub Tab, then click View Certificates button&lt;br /&gt;
4. Go to the Servers tab and press the Add Exception button&lt;br /&gt;
5. Type the location of the website. (e.g. https://www.cgmailbox.com/)&lt;br /&gt;
6. Click on get certificate&lt;br /&gt;
7. Click on Confirm Security Exception&lt;br /&gt;
8. Click OK - OK.&lt;br /&gt;
9. Restart Mozilla Firefox&lt;br /&gt;

= Import a SSL Certificate Into Email Client =

1. Open Outlook (or most mail clients)&lt;br /&gt;
2. Check the box to enable SSL encryption for SMTP and change the port to 465 (Tools - Account Settings - More Settings - Advanced)&lt;br /&gt;
3. Check the box to enable SSL and change the incoming port to: POP3 is 995, IMAP is 993&lt;br /&gt;
4. Click OK - Ok/Close, and restart Outlook.&lt;br /&gt;
5. You will receive a security warning asking if you want to continue using the server. Click on View Certificate.&lt;br /&gt;
6. Click on the details tab and click on Copy to File&lt;br /&gt;
7. Click Next, Next, then click on Browse and Navigate to your desktop. Save the file as mail.domain.cer click Next&lt;br /&gt;
8. Click Finish and you will get a export was successful message.&lt;br /&gt;
9. Right click the mail.domain.cer and then left click on Install Certificate&lt;br /&gt;
10. In the wizard select local machine, then click Next&lt;br /&gt;
11. Click on Place all certificates in the following store, then click Browse and select Trusted Root Certification Authorities, then Ok&lt;br /&gt;
12. Click Next - Finish and you're done after you restart Outlook again.&lt;br /&gt;

&lt;br /&gt;&lt;br /&gt;

''' You can apply these steps to almost any browser or certificate warning'''

= Download CGI Certificates =
&lt;br /&gt;
[http://www.cgi-communication.com/CGI/certs/cgmailbox.com.cer Webmail Certificate]&lt;br /&gt;
[http://www.cgi-communication.com/CGI/certs/mail.cgmailbox.com.cer Mail Client Certificate]
&lt;br /&gt;&lt;br /&gt;</rev>
        </revisions>
      </page>
      <page pageid="9" ns="0" title="T1/DS1">
        <revisions>
          <rev xml:space="preserve">

== T1/DS1 Common Problems and Possible Solutions ==


T1/DS1 circuits are much different than the standard broadband connection to troubleshoot and do require some level of technical knowledge. 

Due to the nature of the service level agreement associated with this type of circuit, CGI-Communication monitors them quite closely. Chances are if the line side of your connection goes down, we will know before you will. The Local Area Network (LAN) side of the connection is not monitored, only the Wide Area Network (WAN) side of the link, so if you have problems with your gateway router or firewall, we may not know about it immediately.

If you have performed the troubleshooting steps below and are still having an issue, ask for a level 2 technician to check the Customer Premise Equipment (CPE) at your location. They should be able to at least tell you if it is a problem on our end and if no problem is found, they can schedule an appointment for you (may be billable) to assist in getting you back up and running. 

1. Can you ping the LAN IP Address of your gateway router or firewall?

2. Can you ping the WAN IP Address of your gateway router or firewall?

3. Does all CPE have power?

4. Have you rebooted the Router or Firewall?

5. Have you rebooted the CPE?

6. Are you getting an Alarm on the Network Interface Device (NID) ?



Contact Technical Support at (520) 421-3333 opt. 2. For after house support, hit option 2, then option 1.</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>