Re: [modwsgi] Really strange problem with passing SSL headers in from Apache

2017-11-14 Thread O haya
, November 14, 2017 at 2:41:50 PM UTC-5, Graham Dumpleton wrote: > > > On 15 Nov 2017, at 3:33 am, O haya <jim...@gmail.com > wrote: > > Ahh. Ok, understood about the header names. > > I think that your environ.wsgi is Python, ultimately, we would want the: > >

Re: [modwsgi] Really strange problem with passing SSL headers in from Apache

2017-11-11 Thread O haya
using headers. The directive: > > SSLOptions +StdEnvVars > > should result in them being passed through in the WSGI environ dictionary > already. > > Graham > > > On 11 Nov 2017, at 4:03 pm, O haya <jim...@gmail.com > wrote: > > Hi, > > I

Re: [modwsgi] Really strange problem with passing SSL headers in from Apache

2017-11-14 Thread O haya
our configuration and provide what it responds with back in the > browser. > > Change any values you think may be sensitive. It will be mainly the keys > rather than values am interested in. > > Graham > > On 12 Nov 2017, at 1:31 am, O haya <jim...@gmail

Re: [modwsgi] Really strange problem with passing SSL headers in from Apache

2017-11-14 Thread O haya
eating CGI like environ, such as occurs with WSGI. There is a CERT > advisory about the problem somewhere. > > So don't use underscores in header names. Also try and use all the SSL_ > values that are already passed in when: > > SSLOptions +StdEnvVars > > is used. > >

[modwsgi] Really strange problem with passing SSL headers in from Apache

2017-11-10 Thread O haya
Hi, I built mod_wsgi using Python 3.6.3 and also with Apache 2.2.29. The Apache is configured for client-authenticated SSL, and I am trying to configure Apache to pass some of the SSL_ variables to a small test Flask application and I am having difficulty getting this working. Here is the

[modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-07 Thread O haya
Hi, I am trying to use WSGI on Apache 2.4.x on CENTOS. I installed mod_wsgi using yum (yum install mod_wsgi), then I copied the mod_wsgi.so to the Apache modules dir and added a Load Module for mod_wsgi. However, when I try to start Apache I am getting this: /apps/apache/bin/apachectl start

Re: [modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-07 Thread O haya
e installation you are using is much > older than the version the mod_wsgi module was compiled for. > > Graham > > On 8 Nov 2017, at 10:37 AM, O haya <jim...@gmail.com > wrote: > > Hi, > > I am trying to use WSGI on Apache 2.4.x on CENTOS. > > I installed mod_wsgi

Re: [modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-07 Thread O haya
rovide the details of what > errors you are getting and what you were doing at that point. I can't guess > why you can't install it without seeing the errors. > > Also use either the mailing list or the issue, and not both. > > Graham > > On 8 Nov 2017, at 3:2

Re: [modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-07 Thread O haya
On Wednesday, November 8, 2017 at 12:05:49 AM UTC-5, O haya wrote: > > Hi, > > Ok thanks for that info. > > I didn't get into detail earlier, but among the attempts that I tried to > build mod-wsgi earlier, I actually DID get the "mod_wsgi-express > start-server&

Re: [modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-07 Thread O haya
6m.a: could not read symbols: Bad value collect2: ld returned 1 exit status error: command 'gcc' failed with exit status 1 On Wednesday, November 8, 2017 at 12:17:06 AM UTC-5, O haya wrote: > > Now I remember, this is what happened when I tried to run "pip3.6 install > mod_wsgi&

Re: [modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-07 Thread O haya
I do wrong that caused adding the LD_LIBRARY_PATH to be a necessity? On Wednesday, November 8, 2017 at 12:21:05 AM UTC-5, O haya wrote: > > Correcting my memory... the "python3.6 setup.py" had the same problem (now > I cannot recall how I got the "mod_wsg

Re: [modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-07 Thread O haya
-3.6.3/lib/python3.6/site-packages/mod_wsgi/server/mod_wsgi-py36.cpython-36m-x86_64-linux-gnu.so: undefined symbol: ap_accept_lock_mech :( ??? Jim On Wednesday, November 8, 2017 at 1:08:53 AM UTC-5, O haya wrote: > > Ok, I am re-reading your page: > > https://code.google.com/a

Re: [modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-09 Thread O haya
Cool! Worked! On Wednesday, November 8, 2017 at 7:04:46 PM UTC-5, Graham Dumpleton wrote: > > Running 'python setup.py install' with APXS environment variable set > should also work. > > On 9 Nov 2017, at 11:03 am, O haya <jim...@gmail.com > wrote: > > YES!! That did

Re: [modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-09 Thread O haya
ave to try later tonight, but just was wondering if you knew the answer to that? The reason for this question is I am pretty sure they don't use "--enable-shared" when they build our Apaches. Thanks for ALL of your help! Jim On Thursday, November 9, 2017 at 6:35:34 AM UTC-5, O haya wrot

Re: [modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-08 Thread O haya
p install --no-cache-dir mod_wsgi > > You likely have a broken mod_wsgi compiled version cached and need for it > to be skipped. > > Graham > > On 8 Nov 2017, at 5:17 pm, O haya <jim...@gmail.com > wrote: > > Oh oh, problem :( > > I added: > > LoadMod

Re: [modwsgi] mod_wsgi and Apache 2.4 on Centos 6.8 - undefined symbol: ap_accept_lock_mech

2017-11-08 Thread O haya
connect out. Thanks! Jim On Wednesday, November 8, 2017 at 6:38:40 PM UTC-5, Graham Dumpleton wrote: > > > On 9 Nov 2017, at 10:37 am, O haya <jim...@gmail.com > wrote: > > Hi, > > I got this when I ran that: > > export AXPS=/apps/httpd-2.4.29/bin/apxs > > p