close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

hcm (HTTP Header Enrichment)

date_range 19-Nov-23

arrow_backward

arrow_forward

Syntax

hcm {
    tag-attribute [tag-attr-name];
    tag-rule rule-name {
        term term-number {
            from {
                destination-address {
                    (any-ipv4 | any-ipv4 except);
                    (any-ipv6 | any-ipv6 except);
                    (any-unicast | any-unicast except);
                    (prefix | prefix except);
                }
                destination-address-range {
                    high address low address <except>;
                }
                destination-port-range {
                    high port-number low port-number;
                }
                destination-ports value;
            }
            then {
                count;
                tag tag-name { 
                    encrypt {
                        hash algorithm;
                        prefix hash-prefix;
                    }
                    ipv4-mask ipv4-mask;
                    ipv6-mask ipv6-mask;
                    ipv4-or-value ipv4-or-value;
                    ipv6-or-value ipv6-or-value;
                    tag-attribute tag-attr-name;
                    tag-header header;
                    tag-separator separator;
                }
            }
        }
    }
    tag-rule-set rule-set-name {
        [rule rule-name];
    }
    profile profile-name {
        tag rule rule-name;
    }
}

Hierarchy Level

content_copy zoom_out_map
[edit services]

Description

Configure the parameters required to support subscriber-aware HTTP header enrichment.

You can add content to the HTTP headers sent back and forth as part of the client-server exchange for subscribers accessing Web-based services. You configure HTTP header enrichment as a service for a subscriber.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 16.1.

Support for Next Gen Services introduced in Junos OS Release 20.2R1 on MX Series routers MX240, MX480 and MX960.

arrow_backward PREVIOUS hash-seed (profile)

NEXT arrow_forward hcm-profile (HTTP Header Enrichment)

Junos CLI Reference

ON THIS PAGE

hcm (HTTP Header Enrichment)

Syntax

Hierarchy Level

Description

Required Privilege Level

Release Information

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Junos CLI Reference

ON THIS PAGE

hcm (HTTP Header Enrichment)

Syntax

Hierarchy Level

Description

Required Privilege Level

Release Information

Related Documentation

Stay in touch