On Monday 21 May 2012 16:21:54 Ajay wrote:
> Kamil,
>
> Thanks for replying. I will upgrade to latest version of Fedora soon. When
> I upgraded my Fedora version last, some new problems started showing. I had
> to spend good amount of time fixing them, so the cautious approach and the
> procrastination in upgrading my system's Fedora version to a latest one.
> But, I will it so soon.
>
> Thanks for trying out the command. The error message you received was quite
> informative. I searched for "SSL_ERROR_RX_RECORD_TOO_LONG" and found the
> following URL,
> http://www.lodesys.com/blog/2009/resolving.php
> which basically says something like that such an error occurs when host
> name and ip address have a mismatch.
>
> The above information gave me an idea about accessing
> https://www.tvg.comthrough curl using ipaddress instead of domain
> name. Therefore, first, I
> typed
> dig https://www.tvg.com
>
> obtained the ip address of tvg domain and then tried accessing it's server
> through it's ip address.
> curl -v http://www.tvg.com
> curl -v 192.168.1.254
>
> I then received the normal output, without any error.

www.tvg.com resolves to 208.88.35.20 on my box and a SSL connection via that
IP address ends up with the exactly same error:

$ curl -v https://208.88.35.20
* About to connect() to 208.88.35.20 port 443 (#0)
* Trying 208.88.35.20...
* connected
* Connected to 208.88.35.20 (208.88.35.20) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* NSS error -12263 (SSL_ERROR_RX_RECORD_TOO_LONG)
* Closing connection #0
* SSL connect error
curl: (35) SSL connect error
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-05-21