Alvaro Lopez Ortega wrote:
> On 13-oct-08, at 06:26, Johnny Robeson wrote:
>
>
>> has anybody tested this yet? and is it really necessary anymore.
>> I don't see this integrated in the code
>>
>
>
> As far as I remember, the main issue was fixed; wasn't it Rui?
>
It was; just rechecked trunk and its fine. So there is no need for
this patch.
There is a little quirk that I didn't yet tracked (I don't think its
cherokee fault) though, when you want to mount the django app in a
subdirectory of the site, eg:
vserver!1!rule!10!match = directory
vserver!1!rule!10!match!directory = /demo
and you have you django apps urls.py as:
urlpatterns = patterns('',
(r'^demo/', include('hello.demo.urls')),
)
django routing does not work as *I* expected (if you think I might be
doing something wrong, please educate me!). to make it work I had to
patch django/core/handlers/wsgi.py by adding:
def __call__(self, environ, start_response):
...
if environ.get('SCGI', '0') == '1':
environ['PATH_INFO'] = environ['SCRIPT_NAME'] + environ['PATH_INFO']
environ['SCRIPT_NAME'] = ''
> There are a couple of variables value that differ from its Apache
> equivalent though. That's something we'll fix as soon as we get a few
> new QA test cases to cover them.
>
Humm, which ones?
Best regards,
Rui Lopes
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
