20👍
I suggest the following approach. In your Django view/template return form to the browser with all the parameters that you want to post as hidden form elements. As soon as the form loads the JavaScript will submit (POST) form to where ever you want.
View:
from django.shortcuts import render_to_response
def view(request):
return render_to_response('test.html', { 'foo': 123, 'bar': 456 })
Template:
<html>
<head>
<title>test</title>
<script type="text/javascript">
function load()
{
window.document.test.submit();
return;
}
</script>
</head>
<body onload="load()">
<form name="test" method="post" action="http://www.example.com">
<input type="hidden" name="foo" value={{ foo }} />
<input type="hidden" name="bar" value={{ bar }} />
</form>
</body>
</html>
9👍
GET parameters always go in the URL, that’s what makes them GET parameters.
It is not possible to redirect using POST parameters (which don’t go in the URL) – this is a restriction of HTTP, not Django.
- Make Django test case database visible to Celery
- How to get the submitted value of a form in a Django class-based view?
- Why does python new york time zone display 4:56 instead 4:00?
- How to use Django variable in JavaScript file?
2👍
I don’t agree with Daniel, there’s a way around the HTTP limitation of redirecting only with get params. what i am thinking of is:
- Redirect to a GET destination with the params you want.
- On the GET page, setup a form with the params you forwarded
- Auto submit the form.
That’s what most file download services do and sometimes even payment pages (Paypal and such). it is indeed a bit ugly (1 more hop) but has it’s own benefits.
- Django form with fields from two different models
- Django docker – could not translate host name "db" to address: nodename nor servname provided, or not known
- Django widget override template