[ 
https://issues.apache.org/jira/browse/MAPREDUCE-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Douglas updated MAPREDUCE-1378:
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.22.0
         Assignee: E. Sammer
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

bq. The motivation behind doing a deep dive into the web app architecture is to 
address other places where user input or OS file system paths are used to build 
links for similar reasons. Let me know if this doesn't make sense.

This makes perfect sense. If you're willing to pursue this, please file a JIRA 
and post your proposal.

+1

I committed this. Thanks E. Sammer!

> Args in job details links on jobhistory.jsp are not URL encoded
> ---------------------------------------------------------------
>
>                 Key: MAPREDUCE-1378
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1378
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.22.0
>            Reporter: E. Sammer
>            Assignee: E. Sammer
>            Priority: Trivial
>             Fix For: 0.22.0
>
>         Attachments: MAPREDUCE-1378.patch
>
>
> The logFile argument in the job links on the JT jobhistory.jsp page is not 
> properly URL encoded leading to links that result in 500 errors. I found the 
> issue while working with the Cloudera distro which contained a plus ('+') in 
> the path which is interpreted as a space character (%20) by Firefox. Here is 
> the (trimmed) URL. Note the hadoop-0.20.1+152 directory which should be 
> hadoop-0.20.1%2B152. I have created a patch against current ASF svn trunk but 
> it is untested (although the jsp compiles to a class file ok).
> A job link from http://host:50030/jobhistory.jsp:
> http://host:50030/jobdetailshistory.jsp?jobid=job_201001141235_0001&logFile=file:/Users/esammer/hadoop-0.20.1+152/logs/history/done/...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to