[
https://issues.apache.org/jira/browse/HADOOP-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125912#comment-13125912
]
Steve Loughran commented on HADOOP-7729:
----------------------------------------
+1
If HTTP/1.0 compatibility isn't an issue, ship it. The only people who would
have a problem are those doing telnet and issuing GET commands by hand, but
they aren't the users we care about here. If you can do that, you know how to
do a netstat -a -p tcp and work out for themselves what they are doing wrong.
Of course, any protocol -HTTP included- that doesn't include some bit of
response from the server is wasting some of the SYN-ACK packet used in setting
up the TCP connection -in an ideal world that is where all protocols ought to
publish some identifier and version number. If the current TCP-based protocols
don't do that, it's not easily fixed.
> Send back valid HTTP response if user hits IPC port with HTTP GET
> -----------------------------------------------------------------
>
> Key: HADOOP-7729
> URL: https://issues.apache.org/jira/browse/HADOOP-7729
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hadoop-7729.txt
>
>
> Often, I've seen users get confused between the IPC ports and HTTP ports for
> a daemon. It would be easy for us to detect when an HTTP GET request hits an
> IPC port, and instead of sending back garbage, we can send back a valid HTTP
> response explaining their mistake.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
