Binary package hint: netcat-openbsd
On Lucid Lynx (Beta 1):
When piping input to netcat-openbsd (the pre-installed netcat on the Amazon EC2 AMIs), standard output is broken.
The following has no output at all: $ printf 'GET / HTTP/1.0\r\n\r\n' | nc www.google.com 80
It works when typing the input on the terminal, but that's not feasible in scripts: $ nc www.google.com 80 GET / HTTP/1.0
HTTP/1.0 302 Found [...] $
It should look like this: $ printf 'GET / HTTP/1.0\r\n\r\n' | nc www.google.com 80 HTTP/1.0 302 Found [...]
netcat-traditional is not affected. Neither is netcat on OpenBSD, nor the "netcat-openbsd" package on Debian.
Binary package hint: netcat-openbsd
On Lucid Lynx (Beta 1):
When piping input to netcat-openbsd (the pre-installed netcat on the Amazon EC2 AMIs), standard output is broken.
The following has no output at all:
$ printf 'GET / HTTP/1.0\r\n\r\n' | nc www.google.com 80
It works when typing the input on the terminal, but that's not feasible in scripts:
$ nc www.google.com 80
GET / HTTP/1.0
HTTP/1.0 302 Found
[...]
$
It should look like this:
$ printf 'GET / HTTP/1.0\r\n\r\n' | nc www.google.com 80
HTTP/1.0 302 Found
[...]
netcat-traditional is not affected. Neither is netcat on OpenBSD, nor the "netcat-openbsd" package on Debian.