16👍
There’s no need for get
.request.META
is a dictionary, and as with all dictionaries, you can perform field lookup in the template using the dot notation: {{ request.META.HTTP_REFERER }}
6👍
Add django.core.context_processors.request
in your settings file in TEMPLATE_CONTEXT_PROCESSORS
then you would be able to use the request
in template without explicitly passing it in request context
.
TEMPLATE_CONTEXT_PROCESSORS = (
'django.contrib.auth.context_processors.auth',
'django.core.context_processors.debug',
'django.core.context_processors.i18n',
'django.core.context_processors.media',
'django.core.context_processors.static',
'django.core.context_processors.request', # this one
)
the in template you could do {{request.META.HTTP_REFERER}}
2👍
Actually the preferred way is to use the next
parameter as documented here
You can do in your template something like this:
<input type="hidden" name="next" value="{{ request.GET.next }}" />
- Systemctl strange error: Invalid arguments
- Django Admin, accessing reverse many to many
- Django – links generated with {% url %} – how to make them secure?
- Django: datetime filter by date ignoring time
Source:stackexchange.com