Thanks David,
After experimenting a lot of times, the final template which worked for me was
LoadModule scgi_module /usr/lib/apache2/modules/mod_scgi.so
AddDefaultCharset utf-8
ServerName www.proto.mydomain
ServerAlias mydomain proto
# handle all requests throug SCGI
SCGIMount /scgi/ 127.0.0.1:3007
Surprisingly, the service is accessed through http://www.proto.mydomain/scgi/
Change proto, mydomain to the actual values.
It is working, with correct presentation of the pages, but I wonder
why /scgi/ works and /dynamic
does NOT.
I am wondering how to remove the /scgi/, but I can live with that.
Will continue to experiment.
Thanks a lot.
Ernesto.
http://adorio-research.org/wordpress/
http://www.extreme.adorio-researh.org/scgi/
On Thu, Aug 12, 2010 at 12:00 AM, wrote:
> Send QP mailing list submissions to
> qp@mems-exchange.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.mems-exchange.org/mailman/listinfo/qp
> or, via email, send a message with subject or body 'help' to
> qp-request@mems-exchange.org
>
> You can reach the person managing the list at
> qp-owner@mems-exchange.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of QP digest..."
>
>
> Today's Topics:
>
> 1. Apache2 configuration for the proto example. (Ernesto Adorio)
> 2. Re: Apache2 configuration for the proto example. (Ernesto Adorio)
> 3. Re: Apache2 configuration for the proto example. (Binger David)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 11 Aug 2010 09:30:00 +0800
> From: Ernesto Adorio
> Subject: [QP] Apache2 configuration for the proto example.
> To: qp@mems-exchange.org
> Message-ID:
>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Thank you David and Mike,
>
> I think the Apache2 server setup for QP is a legitimate area for QP questions.
> I think I got the QP-scgi side correct now. Now I have to fix the
> Apache again. It was working WITHOUT the scgi entry in the config
> dict with the server accessed as http://mydomain:8003.
>
> I just wish the docs contained a working Apache2 config for the proto
> example, so we can concentrate on writing insanely great QP
> applications.
>
> Assuming that the scgi_address field ("127.0.0.1", "3007") was added
> to the config dict,
>
> How do I complete or correct the following skeleton for a virtual host
> which should be accessed as
>
> http://mydomain/proto?
> or as http://proto.mydomain?
> or even as http://mydomain:8003?
>
>
> LoadModule scgi_module /usr/lib/apache2/modules/mod_scgi.so # Ok.
>
>
> AddDefaultCharset utf-8
> ServerName www.mydomain
> ServerAlias mydomain
> DocumentRoot /var/www/
> #ErrorDocument 500 /500.html
> #ErrorDocument 404 /404.html
>
> # handle all requests throug SCGI
> # SCGIHandler On # not allowed here !
> # SCGIServer 127.0.0.1:3007 # not allowed here!
>
> SCGIMount /dynamic 127.0.0.1:3007 # no error here.
> ProxyPass /proto scgi://127.0.0.1:8003/ # no error here.
>
>
> But I can't get the browser to display the scgi app.
>
> Again, TIA.
> -Ernie.
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 11 Aug 2010 15:31:12 +0800
> From: Ernesto Adorio
> Subject: Re: [QP] Apache2 configuration for the proto example.
> To: qp@mems-exchange.org
> Message-ID:
>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi all,
>
> To add further clarity or obfuscation to the discussion, when I tried
> it on my domain,
> the contents of the javascript file proto.js is displayed if
> http://mydomain/proto is the url but an error results if I specified
> http://mydomain/proto/.
>
> Any ideas?? Perplexed...
>
> Ernesto.
>
>
> On Wed, Aug 11, 2010 at 9:30 AM, Ernesto Adorio
> wrote:
>> Thank you David and Mike,
>>
>> I think the Apache2 server setup for QP is a legitimate area for QP
questions.
>> I think I got the QP-scgi side correct now. Now I have to fix the
>> Apache again. It was working WITHOUT the ?scgi entry in the config
>> dict with the server accessed as http://mydomain:8003.
>>
>> I just wish the docs contained a working Apache2 config for the proto
>> example, so we can concentrate on writing insanely great QP
>> applications.
>>
>> Assuming that the scgi_address field ("127.0.0.1", "3007") was added
>> to the config dict,
>>
>> How do I complete or correct the following skeleton for a virtual host
>> which should be accessed as
>>
>> ? ? ? ? ? ? ? ? ? ?http://mydomain/proto?
>> or as ? ? ? ? ? http://proto.mydomain?
>> or even as http://mydomain:8003?
>>
>>
>> LoadModule scgi_module ?/usr/lib/apache2/modules/mod_scgi.so # Ok.
>>
>>
>> ? ?AddDefaultCharset utf-8
>> ? ?ServerName www.mydomain
>> ? ?ServerAlias mydomain
>> ? DocumentRoot /var/www/
>> ? ?#ErrorDocument 500 /500.html
>> ? ?#ErrorDocument 404 /404.html
>>
>> ? ?# handle all requests throug SCGI
>> ? ?# SCGIHandler On ? ? ? ? # not allowed here !
>> ? ?# SCGIServer 127.0.0.1:3007 # not allowed here!
>>
>> ? ?SCGIMount /dynamic 127.0.0.1:3007 ? ?# no error here.
>> ? ?ProxyPass /proto ?scgi://127.0.0.1:8003/ ?# no error here.
>>
>>
>> But I can't get the browser to display the scgi app.
>>
>> Again, TIA.
>> -Ernie.
>>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 11 Aug 2010 07:41:51 -0400
> From: Binger David
> Subject: Re: [QP] Apache2 configuration for the proto example.
> To: QP/QPY Discussion
> Message-ID:
> Content-Type: text/plain; charset=us-ascii
>
> I think it will help to work this out if you omit the
> ProxyPass line from your apache configuration.
> It appears to be provided by the mod_proxy_scgi module.
> The mod_proxy_scgi module might be wonderful, but
> I think it should be left out of the picture at first.
>
> For mod_scgi with Apache2 all you need in the
> configuration is the LoadModule directive and
> the SCGIMount directive.
>
> The "qp -v" command will tell you what handlers are
> listening on what ports, and that can be useful.
>
> Another tool you might find useful here is the
> qp/hub/scgi_util.py file. It submits a little scgi request
> to the port that you name and prints out the
> response.
>
>
> On Aug 11, 2010, at 3:31 AM, Ernesto Adorio wrote:
>
>> Hi all,
>>
>> To add further clarity or obfuscation to the discussion, when I tried
>> it on my domain,
>> the contents of the javascript file proto.js is displayed if
>> http://mydomain/proto is the url but an error results if I specified
>> http://mydomain/proto/.
>>
>> Any ideas?? Perplexed...
>>
>> Ernesto.
>>
>>
>> On Wed, Aug 11, 2010 at 9:30 AM, Ernesto Adorio
>> wrote:
>>> Thank you David and Mike,
>>>
>>> I think the Apache2 server setup for QP is a legitimate area for QP
questions.
>>> I think I got the QP-scgi side correct now. Now I have to fix the
>>> Apache again. It was working WITHOUT the scgi entry in the config
>>> dict with the server accessed as http://mydomain:8003.
>>>
>>> I just wish the docs contained a working Apache2 config for the proto
>>> example, so we can concentrate on writing insanely great QP
>>> applications.
>>>
>>> Assuming that the scgi_address field ("127.0.0.1", "3007") was added
>>> to the config dict,
>>>
>>> How do I complete or correct the following skeleton for a virtual host
>>> which should be accessed as
>>>
>>> http://mydomain/proto?
>>> or as http://proto.mydomain?
>>> or even as http://mydomain:8003?
>>>
>>>
>>> LoadModule scgi_module /usr/lib/apache2/modules/mod_scgi.so # Ok.
>>>
>>>
>>> AddDefaultCharset utf-8
>>> ServerName www.mydomain
>>> ServerAlias mydomain
>>> DocumentRoot /var/www/
>>> #ErrorDocument 500 /500.html
>>> #ErrorDocument 404 /404.html
>>>
>>> # handle all requests throug SCGI
>>> # SCGIHandler On # not allowed here !
>>> # SCGIServer 127.0.0.1:3007 # not allowed here!
>>>
>>> SCGIMount /dynamic 127.0.0.1:3007 # no error here.
>>> ProxyPass /proto scgi://127.0.0.1:8003/ # no error here.
>>>
>>>
>>> But I can't get the browser to display the scgi app.
>>>
>>> Again, TIA.
>>> -Ernie.
>>>
>> _______________________________________________
>> QP mailing list
>> QP@mems-exchange.org
>> http://mail.mems-exchange.org/mailman/listinfo/qp
>
>
>
> ------------------------------
>
> _______________________________________________
> QP mailing list
> QP@mems-exchange.org
> http://mail.mems-exchange.org/mailman/listinfo/qp
>
>
> End of QP Digest, Vol 44, Issue 3
> *********************************
>