No results

    Cookie name-value pair

    In some cases, it is necessary to cookie name-value pair to be inserted in the HTTP header, for example to address BlueCoat SSL inspection re-encrypting with an internal certificate.


    The HTTP cookie entry is passed in the HTTP request header when using the REST API to communicate with the Confluent Schema Registry.


    The Advanced tab allows you to enter name-value pairs in the form of <cookie-name>=<cookie-value> according to MDN WebDocs syntax. Pairs in the list are separated by a semicolon and a space ('; '). 


    Confluent advanced cookie name-value


    If you wish to reference an environment variable, you may do so, wrapped in double braces:


    Confluent advanced cookie environment var