In that case then, if it is a simple test script, post the complete
script as it will make it easier for people to comment on what may be
wrong. It may just be that for URL mapping you are using it may need a
specific URL and just using /webpy/code.py may not work. You may for
example need to say /webpy/code.py/, with a trailing slash. That is
presuming you even have anything mapped at root of application mount
point.
Graham
On Mar 3, 2:54 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I tried this script and it worked.
> So this is a webpy issue.
>
> Luis
>
> On 3 mar, 00:49, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
>
> > Verify that mod_wsgi is working by replacing your web.py script with
> > the mod_wsgi hello world example script. This will eliminate it being
> > a web.py problem. Ie., use:
>
> > def application(environ, start_response):
> > status = '200 OK'
> > output = 'Hello World!'
>
> > response_headers = [('Content-type', 'text/plain'),
> > ('Content-Length', str(len(output)))]
> > start_response(status, response_headers)
>
> > return [output]
>
> > BTW, if running Apache as a service, does the user that Apache runs as
> > have permission to read the files in your htdocs/webpy directory?
>
> > Per the documentation:
>
> > http://code.google.com/p/modwsgi/wiki/DebuggingTechniques
>
> > if in your Apache configuration you change LogLevel directive to:
>
> > LogLevel info
>
> > when your request the URL, do you see messages in your Apache error
> > log file to indicate that mod_wsgi is even loading your script file?
>
> > Graham
>
> > On Mar 3, 2:31 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > > Thanks Graham!
>
> > > I included the WSGIScriptAlias directive as you indicated, and deleted
> > > the .htaccess file.
> > > I am still getting a 404 error, but I guess it has to do with webpy
> > > and not with modwsgi, don't you think?
>
> > > As I said, I'm using the developer version so I hope someone gives me
> > > a hint on how to convert my script into a modwsgi app.
>
> > > Luis
>
> > > On 2 mar, 22:49, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
>
> > > > On Mar 3, 12:34 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > > > > Graham,
>
> > > > > You are right, I'm using Windows (isn't it what dumb people use? :-).
> > > > > Regarding my .htaccess file, this is its content (just like webpy´s
> > > > > sample):
>
> > > > > <Files code.py>
> > > > > SetHandler wsgi-script
> > > > > Options ExecCGI
> > > > > </Files>
>
> > > > > My script file is called "code.py", and it is located in this
> > > > > directory: "C:\xampp\htdocs\webpy" (along with my .htccess file).
> > > > > So based on this information, how should the WSGIScriptAlias directive
> > > > > look?
>
> > > > > Luis
>
> > > > > WSGIScriptAlias /webpy/ "C:/xampp/htdocs/webpy"
>
> > > > If you want all files in that directory treated like they are WSGI
> > > > script files, then must be trailing slash on RHS as well. Thus:
>
> > > > WSGIScriptAlias /webpy/ "C:/xampp/htdocs/webpy/"
>
> > > > This should be in main Apache configuration file, OUTSIDE of any
> > > > Directory containers. The .htaccess file is then not required.
>
> > > > The URL would be:
>
> > > > http://<hostname>/webpy/code.py
>
> > > > Replace '<hostname>' with your actual hostname, or 'localhost' if
> > > > wanting to access it locally.
>
> > > > BTW, the SetHandler in .htaccess file as given by web.py documentation
> > > > will not work if the directories don't have AllowOverride for FileInfo
> > > > set. This isn't explained in documentation on web.py site and probably
> > > > why it didn't work for you in the first place. The documentation on
> > > > web.py site could thus be improved. Using WSGIScriptAlias in main
> > > > Apache configuration avoids the need to do that.
>
> > > > Graham
>
> > > > > On 2 mar, 21:51, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
>
> > > > > > On Mar 3, 10:58 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > > > > > > Dear Graham,
>
> > > > > > > Yes, I just placed the file mod_wsgi.so in the modules folder.
> > > > > > > Is there any other way to do it? I have no idea of what you mean
> > > > > > > by
> > > > > > > 'install' target provided by the makefile.
> > > > > > > How do I use it? I haven't found anything in the docs.
>
> > > > > > If you were using UNIX the 'install' target is the preferred way.
> > > > > > You
> > > > > > didn't say you were using Windows before however, in which case a
> > > > > > manual copy is indeed required.
>
> > > > > > > I haven't put any other configuration besides LoadModule.
> > > > > > > I just followed the instructions in webpy's site.
> > > > > > > As for the configurations guidelines, I supposed they were for
> > > > > > > particular cases. Do I have to configure all these right from the
> > > > > > > start?
>
> > > > > > They are different alternatives depending on what you need to do.
> > > > > > The
> > > > > > most basic one to use is WSGIScriptAlias. This needs to be done in
> > > > > > main Apache configuration and not in .htaccess file. Try that first.
> > > > > > The root URL for your application will be whatever you use as first
> > > > > > argument to WSGIScriptAlias.
>
> > > > > > > I assume that the problem is with the web.wsgifunc function,
> > > > > > > because
> > > > > > > when attempting to visit the site, I get this error:
>
> > > > > > > Error 404
>
> > > > > > Which means that you haven't configured Apache properly for
> > > > > > mod_wsgi,
> > > > > > or if you followed .htaccess example from web.py documentation that
> > > > > > you simply didn't use the correct URL to access the application.
> > > > > > What
> > > > > > URL is used to access the directory you used and what URL did you
> > > > > > use
> > > > > > then to access the actual web.py application? For that matter, what
> > > > > > did you put in the .htaccess file and what did you call your web.py
> > > > > > application script file?
>
> > > > > > > localhost
> > > > > > > 03/02/08 20:55:58
> > > > > > > Apache/2.2.4 (Win32) DAV/2 mod_ssl/2.2.4 OpenSSL/0.9.8e
> > > > > > > mod_autoindex_color PHP/5.2.3 mod_wsgi/2.0c5-TRUNK Python/2.5.1
>
> > > > > > Suggest you use revision_726_2.0c4 and not the latter revision. The
> > > > > > latter is not an official version, but a snapshot to allow some
> > > > > > people
> > > > > > to do some testing and there are some issues with it still.
>
> > > > > > > So it means the module is loaded, isn't it?
>
> > > > > > Yes, that is explained in the compilation instructions document
> > > > > > referenced from installation instructions.
>
> > > > > > Graham
>
> > > > > > > Luis
>
> > > > > > > On 2 mar, 20:36, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
>
> > > > > > > > On Mar 3, 8:55 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> > > > > > > > wrote:
>
> > > > > > > > > I'm trying unsuccessfully to run webpy (developer version)
> > > > > > > > > with
> > > > > > > > > modwsgi.
> > > > > > > > > I'm using Apache 2.2.4 and Python 2.5.1, and the instructions
> > > > > > > > > shown in
> > > > > > > > > the website didn't work.
>
> > > > > > > > > What I did so far is:
> > > > > > > > > 1) Copiedmod_wsgi.so to the modules folder of Apache.
>
> > > > > > > > Do you mean you copied by hand? What was wrong with the
> > > > > > > > 'install'
> > > > > > > > target provided by the makefile?
>
> > > > > > > > > 2) Added the line "LoadModule wsgi_module
> > > > > > > > > modules/mod_wsgi.so" to
> > > > > > > > > httpd.conf.
> > > > > > > > > 3) Created an .htaccess file in my site's folder.
>
> > > > > > > > > The instruccions indicate that I shoud put this line in
> > > > > > > > > code.py:
> > > > > > > > > application = web.wsgifunc(web.webpyfunc(urls, globals()))
>
> > > > > > > > > But I am using the latest developer version, and if possible,
> > > > > > > > > I'd like
> > > > > > > > > to use the " web.auto_application()" feature.
>
> > > > > > > > > Is there any way to make it work?
>
> > > > > > > > Did you read the following document properly?
>
> > > > > > > > http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines
>
> > > > > > > > What configuration besides LoadModule did you put in the main
> > > > > > > > Apache
> > > > > > > > configuration file.
>
> > > > > > > > The example in:
>
> > > > > > > > http://code.google.com/p/modwsgi/wiki/IntegrationWithWebPy
>
> > > > > > > > for latest development version is different, although if it is
> > > > > > > > now
> > > > > > > > called web.auto_application() they must have changed it mid
> > > > > > > > stream.
>
> > > > > > > > There is also a lot of other documentation on the mod_wsgi site.
>
> > > > > > > > Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web.py" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---
