This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
policy-urlset
The following operations can be performed on “policy-urlset”:
update | export | rm | show | add | import |
update policy urlset
Update the specified urlset from the source.
Synopsis
update policy urlset
Arguments
name Name of the urlset to update.
Example
update policy urlset urlset1
export policy urlset
Exports the specified urlset to the URL. Ensure the URL accepts a PUT request for HTTP/HTTPS URL.
Synopsis
export policy urlset
Arguments
name Unique name of the url set. Not case sensitive. Must begin with an ASCII letter or underscore (_) character and must contain only alphanumeric and underscore characters. Must not be the name of an existing named expression, pattern set, dataset, string map, or HTTP callout.
url URL (protocol, host, path and file name) from where the CSV (comma separated file) file will be imported or exported. Each record/line will one entry within the urlset. The first field contains the URL pattern, subsequent fields contains the metadata, if available. HTTP, HTTPS and FTP protocols are supported. NOTE: The operation fails if the destination HTTPS server requires client certificate authentication for access.
Example
export policy urlset urlset1 -url http://www.example.com/PUT_file_1
rm policy urlset
Removes a url set. If the url set is used by an expression in another object, such as a policy, you must remove the object before removing the url set.
Synopsis
rm policy urlset
Arguments
name Name of the url set to remove.
Example
rm urlset urlset1
show policy urlset
Displays information about the configured urlsets.
Synopsis
show policy urlset [
Arguments
name Name of the url set for which to display the detailed information. If a name is not provided, a list of all url sets configured on the appliance is shown.
imported when set, display shows all imported urlsets. Default value: 0
Output
stateflag comment Any comments to preserve information about this url set.
patternCount Number of patterns in this urlset.
url URL (protocol, host, path and file name) from where the CSV (comma separated file) file will be imported or exported. Each record/line will one entry within the urlset. The first field contains the URL pattern, subsequent fields contains the metadata, if available. HTTP, HTTPS and FTP protocols are supported. NOTE: The operation fails if the destination HTTPS server requires client certificate authentication for access.
delimiter CSV file record delimiter.
rowSeparator CSV file row separator.
interval The interval, in seconds, rounded down to the nearest 15 minutes, at which the update of urlset occurs.
MatchedId An ID that would be sent to AppFlow to indicate which URLSet was the last one that matched the requested URL.
canaryUrl Add this URL to this urlset. Used for testing when contents of urlset is kept confidential.
devno count
Example
show policy urlset urlset1
add policy urlset
Adds a url set.
Synopsis
add policy urlset
Arguments
name Unique name of the url set. Not case sensitive. Must begin with an ASCII letter or underscore (_) character and must contain only alphanumeric and underscore characters. Must not be the name of an existing named expression, pattern set, dataset, string map, or HTTP callout.
comment Any comments to preserve information about this url set.
Example
add policy urlset urlset1
import policy urlset
Imports the specified urlset to the Citrix ADC, assigns it the specified name.
Synopsis
import policy urlset
Arguments
name Unique name of the url set. Not case sensitive. Must begin with an ASCII letter or underscore (_) character and must contain only alphanumeric and underscore characters. Must not be the name of an existing named expression, pattern set, dataset, string map, or HTTP callout.
overwrite Overwrites the existing file. Default value: 0
delimiter CSV file record delimiter. Default value: 44
rowSeparator CSV file row separator. Default value: 10
url URL (protocol, host, path and file name) from where the CSV (comma separated file) file will be imported or exported. Each record/line will one entry within the urlset. The first field contains the URL pattern, subsequent fields contains the metadata, if available. HTTP, HTTPS and FTP protocols are supported. NOTE: The operation fails if the destination HTTPS server requires client certificate authentication for access.
interval The interval, in seconds, rounded down to the nearest 15 minutes, at which the update of urlset occurs. Default value: 0 Maximum value: 2592000
privateSet Prevent this urlset from being exported. Default value: 0
subdomainExactMatch Force exact subdomain matching, ex. given an entry ‘google.com’ in the urlset, a request to ‘news.google.com’ won’t match, if subdomainExactMatch is set. Default value: 0
MatchedId An ID that would be sent to AppFlow to indicate which URLSet was the last one that matched the requested URL. Default value: 1 Minimum value: 2 Maximum value: 31
canaryUrl Add this URL to this urlset. Used for testing when contents of urlset is kept confidential.
Example
import policy urlset urlset1 -url http://www.example.com/file_1
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.