Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#53740 - [openbsd-netcat] HTTP response is not displayed at all
Attached to Project:
Community Packages
Opened by Alif (alive4ever) - Friday, 21 April 2017, 13:44 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 22 April 2017, 17:21 GMT
Opened by Alif (alive4ever) - Friday, 21 April 2017, 13:44 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 22 April 2017, 17:21 GMT
|
DetailsDescription:
nc binary provided by openbsd-netcat doesn't work, i.e. HTTP request result isn't displayed at all. Additional info: * package version(s): 1.130_1-1 * config and/or log files etc. Steps to reproduce: Install openbsd-netcat package Make simple http request using nc $ printf 'GET / HTTP/1.0\r\nHost: www.archlinux.org\r\nUser-Agent: wget\r\n\r\n' | nc www.archlinux.org 80 Expected result: nc displays HTTP response HTTP/1.1 301 Moved Permanently Server: nginx/1.10.3 Date: Fri, 21 Apr 2017 13:31:09 GMT Content-Type: text/html Content-Length: 185 Connection: close Location: https://www.archlinux.org/ <html> <head><title>301 Moved Permanently</title></head> <body bgcolor="white"> <center><h1>301 Moved Permanently</h1></center> <hr><center>nginx/1.10.3</center> </body> </html> Actual result: nc doesn't display HTTP response at all. Hint: busybox's nc applet, nc from gnu-netcat, and nmap's ncat command work fine. Only nc from openbsd-netcat is broken. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 22 April 2017, 17:21 GMT
Reason for closing: Not a bug
Additional comments about closing: At most, this is an out of date notification
Saturday, 22 April 2017, 17:21 GMT
Reason for closing: Not a bug
Additional comments about closing: At most, this is an out of date notification
Comment by Alif (alive4ever) -
Friday, 21 April 2017, 14:05 GMT
Rebuilding with latest upstream patches fixes the issue (1.130-3).
Comment by Alif (alive4ever) -
Friday, 21 April 2017, 14:28 GMT
Related Debian bug is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849192
Comment by Doug Newgard (Scimmia) -
Friday, 21 April 2017, 14:43 GMT
Debian report seems to indicate that this is an intentional change in bahavior.