Forum Discussion
JotaCePena_1783
Nimbostratus
Nimbostratushow to redirect http/https to new destination ports
Hi all, I tried to redirect ports 80 and 443 in a VS, this manner:
My VS1 is configured to listening on port 80 and my pool to listening in port 1080
My VS2 is configured to listening on port 44...
Kevin_Davies_40
Nacreous
NacreousOk that tells us a lot. You may find it easier to post output to places like https://gist.github.org and include a link here.
The first curl responds with a redirect that adds a trailing slash and then uses Try it again with the trailing slash... curl http://11.240.64.32:1080/
The second curl was a typo as you used http:// instead https:// and you are lucky at least it gave you a hint.
The third curl responded with another redirect but doesnt tell you the destination in the message. Try the curl again but this time use the -i option to tell curl to include the HTTP headers.
JotaCePena_1783Hera are ouputs Active:In Sync] ~ curl -i https://11.240.64.32:1081/ curl: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. [jcpena@F2000S-SBD1-00A-CORE-C1U1:Active:In Sync] ~
