Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
The Qlik REST Connector is a young and versatile connectivity solution so it’s still lacking some features. One missing point is a proxy authentication so all your REST calls get blocked if your Qlik server (or desktop) is behind a proxy. Btw. Qlik Web Connectors already provide this proxy configuration option.
But there is help if your Proxy works with HTTP Basic Authentication. You can just use the HTTP header Proxy-Authorization within your REST connection.
Copy out this HTTP header from your browser session and use it in the REST connectior dialog. Alternatively, you can encode your proxy credentials (user:pw) yourself with Base64:
Example: user:pw = test:test
HTTP Header:
Proxy-Authorization: Basic dGVzdDp0ZXN0
Now use the header in the REST connector dialog:
Then, test your load script and cross fingers.. 😉
Happy Qliking!
Ralf
Hi Ralf,
I'm running up against an issue trying to connect to an API (I'm just using a dummy one at JSONPlaceholder - Fake online REST API for developers).
I receive an error (HTTP error 407 - Proxy Authorization Required) which has led me to your post!
One thing to clarify though, when you say "Copy out this HTTP header from your browser session" what do you actually mean? Am I supposed to find this somewhere? I had a look at the headers that my browser is sending and I don't have anything regarding proxy-authorization.
What am I missing?
Hi Adam,
what headers is the browser sending when authorizing the proxy, let's say on a normal website you reach out?
Hi Ralf,
Thanks for getting back to me. This is what I see when I go to xhaus.com to view what my browser is sending:
Request parameter | Value |
Requested URI | /headers |
Request Method | GET |
Remote IP Address | 91.229.173.203 |
Remote IP Port | 26650 |
Protocol version | HTTP/1.1 |
HTTP Header* | Value |
Accept | text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 |
Accept-Encoding | gzip, deflate, sdch |
Accept-Language | en-US,en;q=0.8 |
Connection | Keep-Alive |
Host | www.xhaus.com |
Max-Forwards | 10 |
Referer | https://www.google.co.uk/ |
Upgrade-Insecure-Requests | 1 |
User-Agent | Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 |
Via | 1.1 svr-lfl-svwa2.bathempire.local:8081 |
X-Sophos-Meta | e3879be8459357899fdf8a14d56f9f31ce7b295e380decbf30c17b3c5a304a1922683523504570cb9e16d82daf6690af9b05abcccb0fc799f5050bdec0dbd3aefbe2f50e9537afd38a06a52cb80d3976e092b275cdf7be9e |
What does the browser tools show?
Hi Ralf,
Nothing with regards to the proxy at all:
I assume your Proxy doesn't work with HTTP Basic Authentication.
I got it solved:
REST Connector How to configure proxy settings
In an environment that requires all requests go through a forward proxy, the REST Connector requires additional configuration before connections can be made.
Add the following lines in QvRestConnector.exe.config file, which is located C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector:
172.16.16.102 represents the proxy server IP address and 8888 is the port to connect to the proxy server.
For other possible settings, see https://msdn.microsoft.com/en-us/library/kd3cf2ex(v=vs.110).aspx.
The setting can also be set for all applications using .NET framework by modifying the file machine.config, located in C:\Windows\Microsoft.NET\Framework64\vX.X.XXXXX\Config. X.X.XXXX is the version number for the .NET framework installed.
This proxy configuration procedure can be used for other connectors included in Qlik Sense Enterprise for Windows hub: ODBC Connector Package, Salesforce Connector, and DataMarket Connector.
Hello,
On my Qlik Sense Desktop, I have to edit the file located here (it may be hidden)
C:\Users\{my user}\AppData\Local\Programs\Common Files\Qlik\Custom Data\QvRestConnector\QvRestConnector.exe.config
Please note also : the proxy must be exactly the one stored in IE Internet options. As an example if no http, don't add an http (I tried, it doesn't work).
Right now I can connect but I don't get the answer...