On 17 August 2010 13:41, Andy McKay <[email protected]> wrote:
>
> On 2010-08-16, at 6:58 PM, Graham Dumpleton wrote:
>>> Yep that's already set up as a redirect via RewriteRules.
>>
>> Sorry, bit confused. Does the URL the person sees in the browser have
>> the locale in URL or not?
>
> Yes.
>
>> Can I see the full set of rewrite rules you are using as the actual
>> WSGIScriptAliasMatch.
>
> Hmm I'm normally the first to get annoyed by people who say no, but a) it's
> full of lots of irrelevant stuff that will confuse the issue and b) I'd have
> to change it a lot to get around NDA's etc.
>
>> Making various assumptions, sounds like you perhaps should be using
>>
>> WSGIScriptAliasMatch ^/[a-z]{2}(/.*) /home/django/django.wsgi$1
>> application-group=%{GLOBAL}
>
> I will read up on application-group, thanks for the pointer.
You'll only find that documented in changes file for 3.0 (I think).
Is the same as having done:
WSGIScriptAliasMatch ^/[a-z]{2}(/.*) /home/django/django.wsgi$1
WSGIApplicationGroup %{GLOBAL}
Just using the new short hand method.
Graham
>> But you should not be using 'set_script_prefix'. That should not be
>> required because that is what SCRIPT_NAME as set by mod_wsgi is for.
>
> We started using set_script_prefix because there are pages that appear with a
> different pile of URL's depending upon the context the page is viewed in.
> It's a bit of a mess and hack, I'll be the first to admit, but it solved the
> problem at the time. I do know enough that pulling out set_script_prefix will
> trigger a whole pile of failing tests and unhappy stares from various other
> people in the team.
>
> I'll have a look with untired eyes tomorrow based on what you've said.
>
> Thank you.
>
>> You will need to force all to run in same interpreter though using
>> applicaiton-group option.
>>
>> To work out which locale you are in, you would extract it out of
>> SCRIPT_NAME from WSGI environment out of Django request object.
>>
>> Graham
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "modwsgi" 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/modwsgi?hl=en.
>>
>
> --
> Andy McKay, @andymckay
> Django Consulting, Training and Support
>
> --
> You received this message because you are subscribed to the Google Groups
> "modwsgi" 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/modwsgi?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" 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/modwsgi?hl=en.
