Hi Bobby, Great to know you also face this problem!
I'd like to share my work-around for this. I did a small hack in core.clj, add a loader page which use javascript to redirect to the right URL: (GET "/loader" request (str "<script>window.location.href='http://"; (:server-name request) ":" (:server-port request) "'; </script>")) And then fill the loader page as TrackingURL, so, if the storm ui IP:port can be accessed from your client machine, then it should work. Sean On Thu, Feb 27, 2014 at 12:23 AM, Robert Joseph Evans (JIRA) < [email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/STORM-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913094#comment-13913094] > > Robert Joseph Evans commented on STORM-246: > ------------------------------------------- > > I would love it if we could fix this on the YARN side. The problem is > that it would YARN require the proxy to parse HTML/CSS and rewrite the > links. I think this is possible but I am not an expert on HTML, so I > should not have been the one to write the proxy anyways. If anyone can fix > it I would be forever grateful for them to clean up my mess. On that note I > think the MR API has this same problem, it is just that it uses the same JS > libraries that YARN does so it just happens to work. > > > Make the storm ui css/js resource path to be relative so that it can be > rendered in YARN page proxy > > > --------------------------------------------------------------------------------------------------- > > > > Key: STORM-246 > > URL: https://issues.apache.org/jira/browse/STORM-246 > > Project: Apache Storm (Incubating) > > Issue Type: Bug > > Reporter: Sean Zhong > > Priority: Trivial > > Attachments: 001.png > > > > > > > > > -- > This message was sent by Atlassian JIRA > (v6.1.5#6160) >
