On Tue, Feb 17, 2009 at 3:04 AM, Miguel <migue...@gmail.com> wrote:
> [snip]
> params = urllib.urlencode({"Ds_Merchant_Titular":
> Ds_Merchant_Titular, "Ds_Merchant_MerchantCode": Ds_Merchant_MerchantCode})
> #f= urllib2.urlopen("https://sis.sermepa.es/sis/realizarPago
> ",params)
>
> return f -> it doesnt workd
>
> # return
> HttpResponseRedirect("https://sis.sermepa.es/sis/realizarPago",params)
> --> it doesn't work
>
No, it wouldn't. HttpResponseRedirect is documented (
http://docs.djangoproject.com/en/dev/ref/request-response/#django.http.HttpResponseRedirect)
to take a single argument. You can yourself combine params and location
into the url argument to HttpResponseRedirect:
return HttpResponseRedirect("?".join(("
https://sis.sermepa.es/sis/realizarPago",params)))
but that won't force the client browser to use a POST when retrieving the
redirect location. The redirect response contains a status code and
location, there is no field for the server to specify what method should be
used to access the specified location. Standards actually specify that the
browser must use the same method as was used on the original request (which
seems to be what you want), but that is not, in fact, what most browsers
do. See:
http://en.wikipedia.org/wiki/HTTP_302
Karen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
