Rewriting Base URL when passing

[adam estes]

It seems to actually be rewriting the url now. The issue is with how its
doing it

when I visit 69.x.x.x./django/admin/

it rewrites it to 69.x.x.x/admin/

which is then processed by nginx again I'm guessing because it loads the
IPB admin folder, and not the django admin url like it should if it was
being handled by django.

On Wed, Feb 15, 2012 at 3:06 PM, adam estes <wtymdjs at gmail.com> wrote:

> I removed that from both the uwsgi_params and uwsgi_params.default. Still
> isn't working.
>
>
> On Wed, Feb 15, 2012 at 2:49 PM, Valentin V. Bartenev <ne at vbart.ru> wrote:
>
>> On Wednesday 15 February 2012 22:53:56 adam estes wrote:
>> > The problem is that its not going to be just /admin
>> >
>> > There are around 10 urls defined.
>> >
>> > I tried
>> >
>> > location ~ ^/django(?P<django_path>.*?)$ {
>> >                         uwsgi_param PATH_INFO $django_path;
>> >                         uwsgi_pass 127.0.0.1:9001;
>> >                         include uwsgi_params;
>> >                 }
>> >
>> >
>> > Which according to RegSkinner, would match anything after /django
>> >
>> > But this did not work. Its still passing the django parth. What do I do?
>> >
>>
>> Have you looked at your "uwsgi_params" file which you include in the
>> location?
>> So I expect that it sets one more PATH_INFO param to different value.
>>
>>  wbr, Valentin V. Bartenev
>>
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120215/0e62c3e4/attachment.html>