On Dec 31, 2017 7:26 AM, "Sundararajan Seshadri" wrote:
Thanks for the support and responses.
The error was due to an interesting line of code.
I had a middleware where I used:
match = resolve(request.get_full_path()) and this was causing the error I
mentioned.(get_full_path returns the query
Thanks for the support and responses.
The error was due to an interesting line of code.
I had a middleware where I used:
match = resolve(request.get_full_path()) and this was causing the error I
mentioned.(get_full_path returns the query string too.)
I replaced it with
match = resolve(reques
admin/ [name='index']
admin/ login/ [name='login']
admin/ logout/ [name='logout']
admin/ password_change/ [name='password_change']
admin/ password_change/done/ [name='password_change_done']
admin/ jsi18n/ [name='jsi18n']
admin/ r/// [name='view_on_site']
.. (corresponds to the tables defined)
a
Please post your urls.py, this looks strange:
admin/ [name='index']
> admin/ login/ [name='login']
> admin/ logout/ [name='logout']
> admin/ r/// [name='view_on_site']
> admin/ ^(?Prsi|auth)/$ [name='app_list']
> login/ [name='login']
> logout/ [name='logout']
> authissue [name='authissue']
>
--
I do not know the mistake I am likely to be committing. In Django Version
2, I have a feeling that URL matching fails whenever there are query
variables.
When I try to log into Admin module, the login screen comes. But when a
'next' query variable is attached, I get a 404. Similarly when I try
5 matches
Mail list logo
