I'm getting really annoyed by this: every time I need to roll out another 
wsgi application, I make (e.g.) 

   - jinja template with 
   
<form action="crunch" method="post" enctype="multipart/form-data">
   
   - werkzeug app with 
   
werkzeug.routing.Rule( "/", endpoint = "new" ),
werkzeug.routing.Rule( "/crunch", endpoint = "crunch" )

   - apache + mod_wsgi config with 
   
WSGIScriptAlias /foo /var/www/wsgi/foo/wsgi.py

-- and every time requests to /foo work fine and run on_new() and show the 
tempalte, but when I click on the form button, I get a 404 because 
"/crunch" is not found. I.e. the form from jinja template is sending 
/crunch instead of /foo/crunch.

Then I spend an hour or four googling and looking and raw http headers and 
trying to remember how I fixed it the last time.

Can somebody please tell me what tf this is the right way to make it work 
and I promise I'll print it out in bold and staple to my office wall?
(This is on 64-bit centos 6 w/ python-jinja2-26-2.6-2.el6.noarch and 
python-werkzeug-0.8.3-2.el6.noarch. Basic apache config with ssl, a named 
virtual host, and mod_wsgi.)

Thanks in advance

-- 
You received this message because you are subscribed to the Google Groups 
"pocoo-libs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pocoo-libs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to