From abo@dsl.dk Wed May 15 14:20:33 2013 Received: (at submit) by bugs.x2go.org; 15 May 2013 12:20:34 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=HTML_MESSAGE, RCVD_IN_DNSWL_MED,T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2 Received: from eu1sys200aog123.obsmtp.com (eu1sys200aog123.obsmtp.com [207.126.144.155]) by ymir (Postfix) with SMTP id 59C4A5DB1E for ; Wed, 15 May 2013 14:20:33 +0200 (CEST) Received: from mail-oa0-f49.google.com ([209.85.219.49]) (using TLSv1) by eu1sys200aob123.postini.com ([207.126.147.11]) with SMTP ID DSNKUZN9kVSCr7ZepIbe+CQsTg94PhyJ4LiB@postini.com; Wed, 15 May 2013 12:20:33 UTC Received: by mail-oa0-f49.google.com with SMTP id k14so2017625oag.8 for ; Wed, 15 May 2013 05:20:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dsl.dk; s=google; h=x-received:mime-version:x-received:date:message-id:subject:from:to :content-type; bh=X3tPhBomPtExMDLAAUcIoB7uplo6+qAXfjspQLkLWeU=; b=PUHpFv4SbERScyT4pNjNSgyfb8U1vWBS5I/Aq8N4UTny8hC1W+y+baFnNTVENr+gkO SaGZO7F3Waj7+H3S/GA3/8YyZQrUCBaf3KW45tp2q8ziNwvb7hqGDHF+wcl7ytMQyu1z Wed2N9NJYj5NmycoYd+nIj2diBgazyHcmB4k4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=X3tPhBomPtExMDLAAUcIoB7uplo6+qAXfjspQLkLWeU=; b=aw+DcdrlrTGhvq6FvIpmIBkPLVUO+aXuOM730G+cskwRfOFYaRY1nik1DfgAMEU6tA r2DDiQ8nGwl+kTK0rMILM43scsO+aaKq0jU0CDUVmymRxkbLaEwysGqPkhDTT1+2hlVH 6kf0Y2ey1MT0wvPSc/B5Mp1T9feaJ3pXzTvNuDqlpLTL+TyZ2zRVSL/sFdurR70znZY/ qVlZrAiTIIu7X9U8DcfDsYSDjdmYQcngYcuiVpMRg8PFIVNuxKRv+r+jge+5n/Y6RGwP y/hhVRhjmpZ2U6M3KBYkVxgNUzHB+3ASuXBNNL/Pq4ImUFdaZ55Kpc8Gq8XRfA423Omo ddfQ== X-Received: by 10.182.130.138 with SMTP id oe10mr16805711obb.90.1368620432075; Wed, 15 May 2013 05:20:32 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.130.138 with SMTP id oe10mr16805701obb.90.1368620431857; Wed, 15 May 2013 05:20:31 -0700 (PDT) Received: by 10.182.190.17 with HTTP; Wed, 15 May 2013 05:20:31 -0700 (PDT) Date: Wed, 15 May 2013 14:20:31 +0200 Message-ID: Subject: X2gobroker-wsgi variables ignored From: Anders Bruun Olsen To: submit@bugs.x2go.org Content-Type: multipart/alternative; boundary=089e0122fa1cac6e1404dcc0c668 X-Gm-Message-State: ALoCoQmuETqAmpVnODSMmvQ21RGQ7DR7dblMo3x5vMo4Mx9mZpT6dAXxv6kqyKbZDZz1wA0fM7CZ10W9XzQ+KNYl78p0T+VpidqGu8iV7bYbhqfiTN8PNEosozDfUXB5ECBZaJhMyAQIK+03/+5pcjdqiJXwkiso3w== --089e0122fa1cac6e1404dcc0c668 Content-Type: text/plain; charset=UTF-8 Package: x2gobroker Version: 0.0.2.0 and 0.0.2.1 (git master) I am trying to setup x2gobroker served via WSGI with the new x2gobroker-wsgi package. I have opted to setup a vhost that will serve only clients from my LAN and a different one for outside access. For this, I want to point them to different config-files (session profiles) and have discovered that none of the SetEnv statements in the Apache config files are being honored. According to http://stackoverflow.com/questions/9016504/apache-setenv-not-working-as-expected-with-mod-wsgiSetEnv does not result in variables being available in os.environ, but instead in the WSGI request's variable called environ. I can see that the code currently looks in os.environ, and as such, when running through WSGI, only default values are used. You could either look in both os.environ and the WSGI requests environ, or only look in the WSGI request and have code before that, which adds os.environs variables to the WSGI request. -- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature) --089e0122fa1cac6e1404dcc0c668 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Package: x2gobroker
Version: 0.0.2.0 and 0.0.2.1 (git = master)

I am trying to setup x2gobroker serv= ed via WSGI with the new x2gobroker-wsgi package. I have opted to setup a v= host that will serve only clients from my LAN and a different one for outsi= de access. For this, I want to point them to different config-files (sessio= n profiles) and have discovered that none of the SetEnv statements in the A= pache config files are being honored. According to=C2=A0http://stackoverflow.com/questions/9016504/apache-setenv-not-w= orking-as-expected-with-mod-wsgi SetEnv does not result in variables be= ing available in os.environ, but instead in the WSGI request's variable= called environ. I can see that the code currently looks in os.environ, and= as such, when running through WSGI, only default values are used. You coul= d either look in both os.environ and the WSGI requests environ, or only loo= k in the WSGI request and have code before that, which adds os.environs var= iables to the WSGI request.

--
Anders Bruun Olsen
It-ansvarlig
Det Danske= Sprog- og Litteraturselskab
(Society for Danish Language and Literature= )
--089e0122fa1cac6e1404dcc0c668--