A custom origin is a subdomain configured for a specific customer and looks like abc.pubnubapi.com.
Using a custom origin allows PubNub to route traffic per customer when a point of presence (PoP) is not performing well or becomes unavailable. It also allows for custom configurations that may be required for a specific use case or region.
Having a custom origin makes it possible for your application's traffic to appear like it's coming from your own domain, rather than multiple domains.
If required, PubNub also provides TLS certificate hosting. When TLS is used, we would need you to supply us with your own certificate. This service comes with an additional monthly fee.
Requesting a Custom Origin
You can request a custom origin by creating a support ticket with PubNub Support, using the subject "Request Custom Origin." Be sure to provide the following details in the request:
- The PubNub account email that has or will have the paid production key set(s)
- Three choices for your subdomain in order of preference (12 characters or less, like abc.pubnubapi.com)
- The PubNub SDKs you currently use in your applications: SDK language/name and version
- Do you have customers or devices in China?
PubNub Support will provide you with a confirmation on your custom origin name and SDK initialization code for the SDK/version that you use. Once you have it, you can start using it by changing the way you initialize PubNub instance in your SDK.
NOTE: Keep in mind that to improve response times and avoid congestion, browsers have their own limitations to concurrent connections:
|Browser||Connections per host name||Max connections|
|Internet Explorer 9||6||35|
|Internet Explorer Mobile9||6||60|
|Internet Explorer 10||8||17|
|Internet Explorer 11||13||17|
In case of any questions, contact us at firstname.lastname@example.org.