Just pointing out a related thread: https://groups.google.com/forum/#!topic/expath/mZ0BVLNzhe8 Cheers, -carl
On Feb 7, 2014, at 11:59 AM, Marco Lettere marco.lettere@dedalus.eu wrote:
I confirm, the other (only) possibility is to write a custom hostname verifier that should be built into a custom basex build. The best solution is to look at the Certificate's CN and possible alternate names and try to match them in the request. Something like
openssl s_client -connect YOURSSLSERVER
should do on linux with the openSSL client... M.
On 02/07/2014 05:36 PM, Florent Georges wrote:
Hi,
Well, the reason of certificates in HTTPS is to ensure security. If the client cannot match the URL you use the certificate sent back by the server, then it might be another server responding. Or it might be that you access the server with another domain name or IP than the one in the certificate. In that case, JMeter is probably by-passing this and use the server anyway, whilst the HTTP module looks like preventing access (which apparently is mandatory as by RFC 2818 and RFC 6125).
The best option is probably to have a look at the certificate and see what domain name or IP it uses.
Regards,
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk