Discuss mailing list

[Fusl Dash <opennic AT lists.dedilink.eu>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

No, this is a different case here. As Julian already explained, the Linode 
loadbalancer does not act like nginx and therefore does not add an additional 
HTTP-Header (e.g. X-Forwarded-For/X-Real-IP/...), but instead just passes the 
raw TCP connection to the server itself...

... at least from what I understood from his email.

On 06/10/2015 02:22 AM, max bellasys wrote:
> Thanks. The reason I asked was that I have some code for Nginx 
> reverse-proxy with load balancing, and *I think* it addresses your issue 
> assuming you had this set up on your Linode. I went through it pretty deep 
> when I needed to serve multiple domains which shared an app and database 
> resources, and yet had specific other roles and scopes... it sounded like a 
> use-case that matched yours assuming a positive on the question I asked… 
> yet it doesn’t seem like my code applies here.
> 
> All the best on this one. 
> 
> On Jun 9, 2015, at 4:08 PM, Julian De Marchi <julian AT jdcomputers.com.au> 
> wrote:
> 
>> On 09/06/15 17:23, max bellasys wrote:
>>> Are you using Nginx in proxying your requests?
>>
>> Only for FastCGI. The flow goes like this:
>>
>> nodebalancer(lindoe) -> nginx -> fastcgi
>>
>>
>> --------
>> You are a member of the OpenNIC Discuss list. 
>> You may unsubscribe by emailing 
>> discuss-unsubscribe AT lists.opennicproject.org
> 
> 
> 
> 
> 
> --------
> You are a member of the OpenNIC Discuss list. 
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org
> 

- -- 
Best regards

Fusl - root AT meo.ws - http://meo.ws/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJVd4S/AAoJELAaqP3QtzpMknQH/jDH6CP0nEpuNb6MV7VYBfC1
YaQhw508Y93Oq3ImMteaXvRlcK+BnQN/Ha+qBKiH0AvU2IzApkDiRbayJEaB1P1K
CE68r0v2KBPYDb25L2RIvr4GKepONvGgbSkihQEFJ5cC6hlTgDqq2eqZX8O8YtCS
E8JsfM5heaCPMUKCsZ/uKzd/+rDSGJ6bIFgAJi2mVfHfaQ0gpnj9jGoTElsc6Zjn
XMT5vA78M6m+alAJTchCPOLEdmhwlJG/iSMhueZMFP+mkNRAcReMb/opofIDdp0s
ijFOVvHum9SY+7GnrM2YmPOZCg2h7RAwzifVleyZxO38TVFXAsqHo6RFj6gsRG4=
=9wQJ
-----END PGP SIGNATURE-----