How to setup Useresponse behind a HTTPS proxy

Solbjørg,

So, what the void of the problem at all?

Please, describe us what UseResponse must confirm or accept and what should it do with passed data?

In other words, what implementation you want to do using X-Forwarded-For?

This is the problem: Our proxy server accepts a request to useresponse at https://ourdomain.com/useresponse. It then makes a proxy request to a server where useresponse is actually installed at http://ourlocaldomain.com:8080/useresponse including X-Forwareded-For with the value https://ourdomain.com/useresponse

However, Useresponse doesn't use this value to serve script and css stylesheets. Useresponse ALWAYS uses $config['resources']['frontController']['baseUrl']. As I explained in my previous post, with Piwik for instance, there is a config setting to tell the system to use X-Forwarded-For INSTEAD of $config['resources']['frontController']['baseUrl']. That would solve the problem in our case as well I think.

I've noticed that Useresponse is using Zend Framework, and this might be a solution

http://www.dasprids.de/blog/2013/10/11/zend-framework-2-routing-and-reverse-proxies

but I haven't tested it. What do you think?

Solbjørg,

Now it's clear for me.

Currently UseResponse does not provide this capability. We have put this feature in our roadmap up to the stable 3.* release.

We've made allowing proxy in self-hosted version. You just need to add following parameter in your config if you use 3.1.1 release:

1. followProxy = true

This is the example how should it be added to the config:

1. 'frontController' => array(
2. 'baseUrl' => 'http://useresponse/',
3. 'followProxy' => true,
4. 'plugins' => array(

Hello.

How should I configure nginx as a proxy for cloud useresponse?

Now I have created location

1. location /help/ {
2. proxy_pass http://uzap.useresponse.com/;
3. proxy_set_header Host $host;
4. proxy_set_header X-Real-IP $remote_addr;
5. proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
6. proxy_set_header X-Forwarded-Proto $scheme;
7. }

but getting useresponse.com/404 response