mitchell852 commented on a change in pull request #2236: update portal info
bubbles
URL:
https://github.com/apache/incubator-trafficcontrol/pull/2236#discussion_r187354002
##########
File path: traffic_portal/app/src/traffic_portal_properties.json
##########
@@ -306,71 +306,71 @@
},
"multiSiteOrigin": {
"title": "Use Multi Site Origin Feature",
- "desc": "Enable the Multi Site Origin feature for this delivery
service.<br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-multi-site-origin\"
target=\"_blank\">See Multi Site Origin...</a>"
+ "desc": "Enable the Multi Site Origin feature for this delivery
service. Is the Multi Site Origin feature enabled for this delivery service
(True/False).<br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-multi-site-origin\"
target=\"_blank\">See Multi Site Origin.</a>"
},
"orgServerFqdn": {
"title": "Origin Server Base URL",
- "desc": "The Origin Server’s base URL. This includes the protocol
(http or https). Example: http://movies.origin.com"
+ "desc": "The Origin Server’s base URL. This includes the protocol
(http or https). Example: http://movies.origin.com. Must be a domain only, no
directories or IP addresses"
},
"originShield": {
"title": "Origin Shield (Pipe Delimited String)",
- "desc": "Description required"
+ "desc": "Add another forward proxy upstream of the mid caches.
Example: go_direct=true will allow the Mid to hit the origin directly instead
of failing if the origin shield is down. Experimental Feature."
},
"profileId": {
"title": "Delivery Service Profile",
- "desc": "Description required"
+ "desc": "Only used if a delivery service uses configurations that
specifically require a profile. Example: MSO configurations or cachekey plugin
would require a ds profile to be used."
},
"protocol": {
"title": "Protocol",
- "desc": "The protocol to serve this delivery service to the
clients with.<br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#delivery-service\"
target=\"_blank\">See more...</a>"
+ "desc": "Services that use \"HTTP and HTTPS\" will be able to
deliver both types of traffic."
},
"qstringIgnore": {
"title": "Query String Handling",
- "desc": "How to treat query strings.<br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#delivery-service\"
target=\"_blank\">See more...</a>"
+ "desc": "How to treat query strings:<br><br><ul><li>0 use in cache
key and hand up to origin: Each unique query string is treated as a unique
URL.</li><li>1 Do not use in cache key, but pass up to origin: 2 URLs that are
the same except for the query string will match and cache HIT, while the origin
still sees original query string in the request.</li><li>2 Drop at edge: 2 URLs
that are the same except for the query string will match and cache HIT, while
the origin will not see original query string in the
request.</li></ul><b>Note:<b> Choosing to drop query strings at the edge will
preclude the use of a Regex Remap Expression. <a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#regex-remap-expression\"
target=\"_blank\">See Regex Remap Expression</a><br>To set the qstring without
the use of regex remap, or for further options, <a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#qstring-handling\"
target=\"_blank\">See Qstring Handling</a><br>"
},
"rangeRequestHandling": {
"title": "Range Request Handling",
- "desc": "How to treat range requests.<br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#delivery-service\"
target=\"_blank\">See more...</a>"
+ "desc": "How to treat range requests.<br><br><ul><li>0: Do not
cache (ranges requested from files that are already cached due to a non range
request will be a HIT)</li><li>1: Use the <a
href=\"https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/background_fetch.en.html\"
target=\"_blank\">background_fetch plugin.</a></li><li>2: Use the
cache_range_requests plugin.</li></ul>"
},
"regexRemap": {
"title": "Regex remap expression",
- "desc": "Regex Remap rule to apply to this delivery service at the
Edge tier.<br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#delivery-service\"
target=\"_blank\">See more...</a>"
+ "desc": "Allows remapping of incoming requests URL using regex
pattern matching to search/replace text.<br><br><a
href=\"https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_remap.en.html\"
target=\"_blank\">See ATS documentation on regex remap</a><b>Note:<b> You will
not be able to save a Regex Remap Expression if you have Query String Handling
set to drop query strings at the edge. <a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#regex-remap-expression\"
target=\"_blank\">See Regex Remap Expression</a>"
},
"regionalGeoBlocking": {
"title": "Regional Geoblocking",
- "desc": "Description required"
+ "desc": "(For HTTP routed delivery services only) Define regional
geo-blocking rules for delivery services in a JSON format and set it to
True/False. <a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/quick_howto/regionalgeo.html#configure-regional-geo-blocking-rgb\"
target=\"_blank\">See Regional Geo-blocking</a>"
},
"remapText": {
"title": "Raw remap text",
"desc": "For HTTP and DNS delivery services, this will get added
to the end of the remap line on the cache verbatim. For ANY_MAP delivery
services this is the remap line."
},
"routingName": {
"title": "Routing Name",
- "desc": "The routing name to use for the delivery FQDN, i.e.
routing-name.deliveryservice.cdn-domain. It must be a valid hostname without
periods."
+ "desc": "The routing name to use for the delivery FQDN, i.e.
routing-name.deliveryservice.cdn-domain. It must be a valid hostname without
periods. Typical values would be ccr, edge and cdn."
Review comment:
There are no typical values I don't think. It can be whatever you want it to
be.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services