MarcoX wrote: > Peter and Daniel, thanks for the reply. > I must use the POST method because the external site WANT a post > method. > parameter2 is a "stupid" info that the external site required. > I try with your (simple) solution, a hidden html form with a > javascript redirect...
I had to do something similar for PayPal. I did it by changing the action="" in a confirmation form to point to PayPal. Instead of form POSTing back to me and trying to redirect POST which doesn't work, it POSTs directly to PayPal. The form was constructed to contain all the things PayPal wanted in hidden fields. In PayPal's instance it doesn't matter that user can change values(they are checked elsewhere, when PP notifies us of payment) but it may in your situation. Depending on what 3rd party site does/wants another way to do this is to use something like urllib2 and POST to 3rdpary in your view code, slurp the response and send it back to user. It will have 3rdparty content but come from your server, which is probably gonna cause problems. -- Norman J. Harman Jr. Senior Web Specialist, Austin American-Statesman ___________________________________________________________________________ You've got fun! Check out Austin360.com for all the entertainment info you need to live it up in the big city! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
