Knowledge Base » General

Contents

Why am I not receiving notifications to my HTTPS URL? [49]

Notifications sent from some MX Telecom products (such as gateways and CMX2) can be protected using SSL if you specify an HTTPS URL as the destination.

If you do not receive notifications to an HTTPS URL, but you can receive them over standard HTTP, a possible cause is that we do not recognise and trust your server's security certificate.

We use the list of trusted certification authorities in Sun's JDK version 5.

If your certificate is from a different authority, there are two possible solutions:

  • we can issue you a certificate that we trust, free of charge. This would not be trusted by most browsers, so this solution is only suitable if the notification URL is on a different IP or port to other traffic.
  • you could obtain an additional certificate from one of the trusted certification authorities.

Why am I receiving unexpected characters in an HTTP response? [50]

A possible cause of unexpected characters in an HTTP response from an MX Telecom gateway is that the gateway is using "chunked" transfer coding, which is part of the HTTP 1.1 specification (see details on W3C site here).

The chunked encoding puts extra characters in the response body to indicate the size of each part of the message, such as the "b" and "0" in the example response below. Note the "Transfer-Encoding: chunked" header.

Chunking would normally be handled automatically by the HTTP implementation you are using to interface with the gateway. You may see these characters while connecting to the gateway via telnet for troubleshooting purposes, but they are not cause for concern.

HTTP /1.1 200 OK
Date: Wed, 22 Jun 2008 13:45:33 GMT
Server: Apache
Transfer-Encoding: chunked
Content-Type: text/plain;charset=US-ASCII

b
MESSAGE123

0