Skip to content

special case for null XFCC value #6

@tfynes-pivotal

Description

@tfynes-pivotal

When XFCC is optional at the load-balancer level, it always adds the XFCC http header which results in the ClientCertificateMapper warning that there's an illegal value. We should have a special case for XFCC header having an empty value as this does not warrant a warning message.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions