Skip to content
This repository has been archived by the owner on Nov 13, 2018. It is now read-only.

Commit

Permalink
add document for the NGB feature
Browse files Browse the repository at this point in the history
  • Loading branch information
nbaoping committed Mar 14, 2016
1 parent b9f9622 commit 62f950e
Showing 1 changed file with 27 additions and 0 deletions.
27 changes: 27 additions & 0 deletions docs/source/admin/traffic_router.rst
Original file line number Diff line number Diff line change
Expand Up @@ -313,3 +313,30 @@ Sample Message
| | | NXDOMAIN (the domain/name requested does not exist) |
+------+---------------------------------------------------------------------+-----------------------------------------------------+

.. _rl-tr-ngb:

GeoLimit Failure Redirect feature
======

Overview
--------
This feature is also called 'National GeoBlock' feature which is short for NGB feature. In this section, the 'NGB' will used for this feature.

In the past, if the Geolimit check fails (for example, the client ip is not in the 'US' region but the geolimit is set to 'CZ + US'), the router will return 503 response; but with this feature, when the check fails, it will return 302 if the redirect url is set in the delivery service.

The Geolimit check failure has such scenarios:
1) When the geolimt is set to 'CZ + only', if the client ip is not the the CZ file, the check fails
2) When the geolimit is set to any region, like 'CZ + US', if the client ip is not in such region, the check fails


Configuration
--------
To enable the NGB feature, the DS must be configured with the proper redirect url. And the setting lays at 'Delivery Services'->Edit->'GeoLimit Redirect URL'. If no url is put in this field, the feature is disabled, or it's enabled.

The url has 3 kinds of formats, which have different meanings:
1. URL without domain
If no domain is in the url (like 'vod/dance.mp4'), the router will try to find a proper cache server and return the redirect url with the format like 'http://<cache server name>.<delivery service's FQDN>/<configured relative path>'
2. URL with domain that matches with the delivery service
The URL has domain and the domain matches with the delivery service. For this URL, the router will also try to find a proper cache server and return the same format url as point 1.
3. URL with domain that doesn't match with the delivery service
The URL has domain but the domain doesn't match with the delivery service. For this URL, the router will return the configured url directly to the client.

0 comments on commit 62f950e

Please sign in to comment.