Re^3: 400 bad request curl post

Replies are listed 'Best First'.
Re^4: 400 bad request curl post by kschwab (Vicar) on Dec 06, 2018 at 15:37 UTC
His client is also a CGI script...see the last few lines.	[reply]
Re^5: 400 bad request curl post by 1nickt (Canon) on Dec 06, 2018 at 16:34 UTC
Sorry, but no, his code only implements a client with LWP and makes a request, then prints out something from the response. I think you're misunderstanding what a "CGI script" is. (Here's a recent article which, although its main point is to urge that new server-side code developed in Perl should avoid CGI.pm, provides some good terminology definitions. Note that the OP's script is not serving anything but simply trying to fetch the content of a web page.) The way forward always starts with a minimal test.	[reply]
Re^6: 400 bad request curl post by poj (Abbot) on Dec 06, 2018 at 16:57 UTC
makes a request, then prints out something from the response with `print "Content-type: text/html\n\n";` in between	[reply] [d/l]
Re^6: 400 bad request curl post by kschwab (Vicar) on Dec 07, 2018 at 22:55 UTC
I respectfully disagree. It prints out the "Content-type:" header, and and dumps out some html. So, if it's dropped into the right place, it certainly is a "CGI script". It may get the content via LWP, but that doesn't change anything. You can write a "cgi script" in /bin/sh. If it happens to get it's content with curl that doesn't suddenly make it not a CGI script. CGI.pm has nothing to do with anything at all in this case.	[reply]
Re^7: 400 bad request curl post by 1nickt (Canon) on Dec 08, 2018 at 12:39 UTC