Hi,
The warning messages are likely harmless. They are probably complaints
about conflicts if the main subject name is repeated as a subject
alternative name. This has been addressed via TS-3243.
I've successfully tested a basic wildcard certificated in 5.2/master.
But obviously we must be doing something different. Can you share your
wildcard certificate so I better replicate your case?
Thanks,
Susan
On 1/27/2015 9:05 PM, Esmq wrote:
hi,all
i have just upgraded ts 5.1.1 to 5.2.0,
and make no change to the configuration (using the previous working
config of version 5.1.1)
after toggle to 5.2.0, i found following warning message in diag.log,
which all good in 5.1.1.
[Jan 28 10:35:13.128] Server {0x2b34fdd3b620} NOTE: loading SSL
certificate configuration from
/home/trafficserver/etc/ssl_multicert.config
[Jan 28 10:35:13.130] Server {0x2b34fdd3b620} WARNING: previously
indexed 'daily.bb.test.com' with SSL_CTX 0x1, cannot index it with
SSL_CTX #2 now
[Jan 28 10:35:13.130] Server {0x2b34fdd3b620} WARNING: previously
indexed wildcard certificate for '*.sslbbs.example.com' as
'com.example.sslbbs.', cannot index it with SSL_CTX #4 now
furthermore, ts crash when processing the request that using
whildcard ssl certificate...
