To reproduce this problem .
First , using openssl generate a certificate for www.example.com domain. and deploy svn + https with this ssl certificate.
If the www.example.com deployed on 192.168.11.123. then while user visit the svn server using ip. not ssl certificate.
The following error will be show. And if we clone svn from svn native command. it will be ok.
```
Error updating working copy: Command failed with error #1!
COMMAND
svn --non-interactive --no-auth-cache --trust-server-cert --username '********' --password '********' info --xml 'https://********@192.168.**.*7/svn/dy_vod_review_center'
STDOUT
<?xml version="1.0" encoding="UTF-8"?>
<info>
STDERR
svn: E170013: Unable to connect to a repository at URL 'https://********@192.168.**.**7/svn/dy_vod_review_center'
svn: E230001: Server SSL certificate verification failed: certificate issued for a different hostname, issuer is not trusted
```
can we just trust local ssl certificate