hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7729) Send back valid HTTP response if user hits IPC port with HTTP GET
Date Mon, 10 Oct 2011 10:28:29 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123989#comment-13123989

Steve Loughran commented on HADOOP-7729:

Todd, If there's one thing I'd change, it'd be create a wiki page talking about this problem
and include the URL in the response -it's what HADOOP-7469 did for connectivity issues. The
people getting confused this way are often new to Hadoop, and a wiki page can give them more
detail on what they need to look for instead, including the various configuration files that
will tell them what port the HTTP server is on. 

Now, if you are really devious and the Server instance was told the port the HTTP server for
that service was up on, it could give the user the right URL (ignoring multiple hostname issues).
I wouldn't try and 30x back as that would only create more confusion.

Incidentally, what if the client is an HTTP1.0 browser? Shouldn't the HTTP version be grabbed
from the incoming request? Or is that getting too close to building a mini-web-server?
> 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


View raw message