You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue showed up at updates from 2.0.30 to 2.0.31 (or 3.0.8) because we happend to have a Root certificate we loaded which had the subject and issuer in the header.
I suspect from the changes that it is the fix for this issue: #1568 which caused this.
From my testing it is any text which is not whitespace before the marker which triggers this, the actual certificate does not appear to matter.
The text was updated successfully, but these errors were encountered:
This issue showed up at updates from 2.0.30 to 2.0.31 (or 3.0.8) because we happend to have a Root certificate we loaded which had the subject and issuer in the header.
I suspect from the changes that it is the fix for this issue: #1568 which caused this.
From my testing it is any text which is not whitespace before the marker which triggers this, the actual certificate does not appear to matter.
The text was updated successfully, but these errors were encountered: