It looks like a proxy in the middle is dropping your connection without sending data, the recv() call failed. Since you got the 301 redirect correctly, that indicates the Elecraft http server is able to at least return headers, you're just having issues with the content body, which is normally where a transparent proxy comes into play (they tend to just forward headers). Very likely, the proxy is having difficulties getting a response from the Elecraft server/having an issue forwarding the response along, so you never receive the response body. This could be an internal networking issue within Verizon, a networking issue between Verizon and Elecraft, a mis-configuration/problem on/with the proxy, or something on the Elecraft server side that's preventing the connection.
All of the above are unfortunately in the hands of the Verizon engineers (or potentially the company Elecraft uses for hosting if they are blocking the requests, but seeing as headers are being passed, more than likely it's on the proxy side). Of course, this assumes there is a transparent proxy in the middle, it's hard to know for sure, but seems the likely cause. David On Sun, Jan 3, 2016 at 4:34 PM, AB2TC - Knut Spang <[email protected]> wrote: > Hi, > > I did that and here is what I got: > > C:\Users\AB2TC\Desktop\Installs\curl\curl_7_46_0_openssl_nghttp2_x64>curl > -vL http://www.elecraft.com > * Rebuilt URL to: http://www.elecraft.com/ > * Trying 63.249.121.93... > * Connected to www.elecraft.com (63.249.121.93) port 80 (#0) > > GET / HTTP/1.1 > > Host: www.elecraft.com > > User-Agent: curl/7.46.0 > > Accept: */* > > > * Recv failure: Connection was reset > * Closing connection 0 > curl: (56) Recv failure: Connection was reset > > > There was a very long delay (minutes) between the "Accept" message and the > "Recv failure" message. > > AB2TC - Knut > > > > C:\Users\AB2TC\Desktop\Installs\curl\curl_7_46_0_openssl_nghttp2_x64> > > > On 1/3/2016 5:07 PM, David Orman wrote: > > Try curl -vL http://www.elecraft.com > > It's doing a redirect you need to follow, this should help. > > David > > On Sun, Jan 3, 2016 at 3:40 PM, ab2tc <[email protected]> wrote: > >> Hi, >> >> I am on 7 and I did succeed in finding "curl" and installing it. Here is >> the >> output from running your suggested command line in a command prompt: >> >> C:\Users\AB2TC\Desktop\Installs\curl\curl_7_46_0_openssl_nghttp2_x64>curl >> -v >> htt >> p://elecraft.com >> * Rebuilt URL to: http://elecraft.com/ >> * Trying 63.249.121.93... >> * Connected to elecraft.com (63.249.121.93) port 80 (#0) >> > GET / HTTP/1.1 >> > Host: elecraft.com >> > User-Agent: curl/7.46.0 >> > Accept: */* >> > >> < HTTP/1.1 301 Moved Permanently >> < Date: Sun, 03 Jan 2016 21:33:57 GMT >> < Server: Apache/2.2.3 (CentOS) >> < Location: http://www.elecraft.com/ >> < Content-Length: 309 >> < Connection: close >> < Content-Type: text/html; charset=iso-8859-1 >> < >> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >> <html><head> >> <title>301 Moved Permanently</title> >> </head><body> >> Moved Permanently >> >> <p>The document has moved here < <http://www.elecraft.com/> >> http://www.elecraft.com/> .</p> >> <hr> >> <address>Apache/2.2.3 (CentOS) Server at elecraft.com Port 80</address> >> </body></html> >> * Closing connection 0 >> >> C:\Users\AB2TC\Desktop\Installs\curl\curl_7_46_0_openssl_nghttp2_x64> >> >> >> It seems to confirm the notion that it connects to elecraft.com but >> fails to >> open the http connection. Maybe some network guru can make sense of the >> messages above. >> >> AB2TC - Knut >> >> >> David Orman wrote >> > Sounds like Verizon has a transparent proxy in the middle, and something >> > is >> > goofing up there. Lots of ISPs do this kind of thing for content >> > filtering/caching/etc, unfortunately, and if that proxy doesn't serve >> the >> > page properly, it'll look like an issue with the site itself. Hopefully >> > they'll resolve it for you all. If someone with the issue has access to >> > linux/curl, try: >> > >> > curl -v http://elecraft.com >> > >> > You'll see where things 'stall' in the HTTP session. >> > >> > David >> > >> > On Sat, Jan 2, 2016 at 2:04 PM, todd ruby < >> >> > todd@ >> >> > > wrote: >> > <snip> >> >> >> >> >> >> -- >> View this message in context: >> http://elecraft.365791.n2.nabble.com/Elecraft-website-and-Fios-tp7612185p7612235.html >> Sent from the Elecraft mailing list archive at Nabble.com. >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[email protected] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: <http://www.qsl.net/donate.html> >> http://www.qsl.net/donate.html >> Message delivered to [email protected] >> > > > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [email protected]
