http://qs321.pair.com?node_id=1180520


in reply to Re: HTTPS returning 400 from Linux but 200 OK from Windows
in thread HTTPS returning 400 from Linux but 200 OK from Windows

I found a 5.18 perl on a network adjacent SuSE 12sp1 server

me@linux:/home/rpollard> export HTTPS_PROXY='http://user:pass@proxy:80 +80' me@linux:/home/rpollard> echo $HTTPS_PROXY http://user:pass@proxy:8080 me@linux:/home/rpollard> curl https://www.google.com <HTML><HEAD><meta http-equiv="content-type" content="text/html;charset +=utf-8"> <TITLE>302 Moved</TITLE></HEAD><BODY> <H1>302 Moved</H1> The document has moved <A HREF="https://www.google.se/?gfe_rd=cr&amp;ei=6T-MWJGBLsiq8weZ_YCIA +Q">here</A>. </BODY></HTML> me@linux:/home/rpollard> perl GetTest.pl 400 Bad Request at GetTest.pl line 16. me@linux:/home/rpollard> unset HTTPS_PROXY me@linux:/home/rpollard> echo $HTTPS_PROXY me@linux:/home/rpollard> curl https://www.google.com curl: (6) Could not resolve host: www.google.com me@linux:/home/rpollard> perl GetTest.pl 500 Can't connect to google.com:443 (Bad hostname) at GetTest.pl line +16. me@linux:/home/rpollard> perl -v This is perl 5, version 18, subversion 2 (v5.18.2) built for x86_64-li +nux-thread-multi Copyright 1987-2013, Larry Wall Perl may be copied only under the terms of either the Artistic License + or the GNU General Public License, which may be found in the Perl 5 source ki +t. Complete documentation for Perl, including FAQ lists, should be found +on this system using "man perl" or "perldoc perl". If you have access to + the Internet, point your browser at http://www.perl.org/, the Perl Home Pa +ge.
That is using the same test script as in the root node. I think this shows both curl and perl are using the same HTTPS_PROXY here. Now I have a more modern Perl, I will install LWP::ConsoleLogger and see what that tells me.

Cheers,
R.

Pereant, qui ante nos nostra dixerunt!

Replies are listed 'Best First'.
Re^3: HTTPS returning 400 from Linux but 200 OK from Windows
by Random_Walk (Prior) on Jan 28, 2017 at 08:22 UTC

    Server is all locked down, no gcc/cc etc and seos won't even let me install gcc, so I can't cpan LWP::ConsoleLogger. Now I can either go through the full change cycle to get a test server, or use curl in my scripts to pull back the data form the REST API I am after, then parse it from there. Neither choice appeals

    Cheers,
    R.

    Pereant, qui ante nos nostra dixerunt!