Limitations

This section highlights the limitations existing in the current release:

  • X-header insertion in the Response packet is not supported.

  • X-header encryption with RSA and RC4MD5 is supported, but not supported with AES.

  • Monitor protocol for X-header is not supported.

  • Insertion of the following X-header fields is not supported in a packet:

    • QoS

    • UIDH

    • Customer ID

    • Hash Value

    • Time of the Day

    • RADIUS String

    • Session-Id

    • Congestion Level

    • User-Profile

  • Parsing and buffering of the HTTP header will be done only if the rulebase has any x-header format configured with x-header fields explicitly set to delete-existing. For operators not using x-header delete-existing, no overhead for parsing or buffering will be seen.