Hi Prasad,

I'm pulling this over to the user@knox mailing list.  Please subscribe to that 
here: http://knox.apache.org/mail-lists.html.

I just checked the OpenWeatherMap API and I noticed that they've changed their 
AppId so I'm getting a 401.
curl 
'http://api.openweathermap.org/data/2.5/weather?zip=95054,us&appid=2de143494c0b295cca9337e1e96b00e0'
The new one is
curl 
'http://api.openweathermap.org/data/2.5/weather?zip=95054,us&appid=44db6a862fba0b067b1930da0d769e98'
But that results in a 401.  I'll have to update the tutorial to reflect the 
fact that they change their AppId.

So I don't know what the 500 error might be.  Can you share anything from your 
gateway.log file that might provide some insight into the issue?

To answer your other question about non-REST endpoints the answer is yes.  Knox 
can be used in front of most HTTP endpoints with sufficient.  In the installed 
data/services directory you will see several existing UI integrations.  One of 
which is hdfsui which may cover your NN question.  The up.com would be a new 
integration but might look similar to the hdfsui integration.

Kevin.

From: "Prasad R. Nuamatha" <[email protected]<mailto:[email protected]>>
Date: Monday, February 29, 2016 at 1:17 AM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Knox

Hi Kevin,
I am trying to use the following to add a service but am running into issues 
like server error etc etc.. Not sure if you had any comments from users with 
the issues of this implementation. Sorry not many users have posted on this, 
hence the questions.
http://kminder.github.io/knox/2015/11/16/adding-a-service-to-knox.html

Also just a quick question, can we simply front end the URL with knox. For 
Example :  http://namenode:50070/dfshealth.html#tab-overview  or 
http://www.up.com<http://www.up.com/> which are not necessarily rest calls ?

Thanks for your time
Prasad


**



This email and any attachments may contain information that is confidential 
and/or privileged for the sole use of the intended recipient. Any use, review, 
disclosure, copying, distribution or reliance by others, and any forwarding of 
this email or its contents, without the express permission of the sender is 
strictly prohibited by law. If you are not the intended recipient, please 
contact the sender immediately, delete the e-mail and destroy all copies.

**

Reply via email to