Do not do this:
                         #"strip-request-uri" => "w2p/"
instead in the web2py folder create a file routes.py that contains

routes_in=(('/w2p/(?<a>.*)','/$a'),)
routes_out=(('/(?<a>.*)','/w2p/$a'),)

this should solve your problem assuming you build all your inner
references using {{=URL(...)}} or using relative paths. Let me know if
it does not solve it.

Massimo

On May 20, 1:58 pm, giohappy <gioha...@gmail.com> wrote:
> No way, url rewrite doesn't solve it. Maybe it's my ignorance, but it
> seems that the lighttpd fastcgi system override it, or maybe only for
> web2py as we involke the fastcgihandler as a 404-error handler.
> If someone has tips to share, he's very welcome! :)
>
> giovanni
>
> On 20 Mag, 19:30, giohappy <gioha...@gmail.com> wrote:
>
> > Thanks Mark.
> > I've digged the problem with a rudimental debug, and I can see from
> > the response headers that it's an "invalid application" error, as
> > web2py looks for /var/www/lighttpd/web2py/applications/w2p, while the
> > last key should be stripped.
> > Lighttpd comes with a strip-request-uri, but it seems a bit buggy. In
> > my case it completely strips the request uri, and gives strange
> > characters as output, so I recieve obviously an "invalid path" error
> > from web2py.
> > I'll try with rewrite urls, but I thought it coud cause problems to
> > the internal rewrite rules of web2py... but your experience is
> > different. I'll go for it, and let you know.
>
> > giovanni
>
> > PS: web2py developers, could we find a solution for this? Maybe a
> > configuration option? I know web2py is zero-configuration... but this
> > could worth a one-line file! :)
>
> > On 20 Mag, 19:08, Mark Larsen <larsen...@gmail.com> wrote:
>
> > > > 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-...)
> > > 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to