> but that configuration doesn't fit my needs. > I've tried setting the following config, but it always results with an > "Invalid request". I suppose it's due to the uri parsing, but I can't > solve it as I'm quite new to Lighttpd. > Any ideas? >
Giovanni, I had the same problem with web2py, apache2 and mod_wsgi. Unless I'm missing something huge, much of web2py (the URL function for example) is wired to have your handler at the root of the webserver. I'm still surprised more web2pyers haven't come up against this limitation. Regardless, I fixed it with apache's mod_rewrite. I believe lighttpd has similar functionality (I'm not a lighty user). Perhaps something like --> url.rewrite = ( “^/appName(.*)$” => “/subFolder/appName$1” ) This would redirect the URLs web2py is spitting out to the proper lighttpd path. I also wrote about in the Wiki here (https://mdp.cti.depaul.edu/wiki/default/page/56ec0fa4-0a01-4e5f-b0d5-1bef446f3df7) but it looks like that is eating my mark-up (A bug in the wiki?). Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
