[jira] [Updated] (TS-3422) Mismatched ID in certificate indexing warnings

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-3422:
------------------------------
    Fix Version/s:     (was: 6.2.0)
                   7.0.0

> Mismatched ID in certificate indexing warnings
> ----------------------------------------------
>
>                 Key: TS-3422
>                 URL: https://issues.apache.org/jira/browse/TS-3422
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: SSL
>            Reporter: James Peach
>            Assignee: Susan Hinrichs
>             Fix For: 7.0.0
>
>
> Previously, the SSL certificate SNI collision warnings always referenced the pointer value ({{%p}}) of the context so that you could use SSL diagnostic output to find out which certificates contained the collision.
> Now, the relevant warnings are:
> {code}
>         Warning("previously indexed wildcard certificate for '%s' as '%s', cannot index it with SSL_CTX #%d now",
>             name, reversed, idx);
> {code}
> This message has the index number rather than the pointer value.
> {code}
>       Warning("previously indexed '%s' with SSL_CTX %p, cannot index it with SSL_CTX #%d now", name, value, idx);
> {code}
> This message shows the pointer value of the existing context and the index value of the new one.
> To make these more helpful, we should use consistent IDs across all the messages. Either pointer value or index is probably OK, though AFAICT indices can be reused after collisions which could be confusing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)