Hi all, Recently I have been developing an application that receives files from jobs (bash scripts) running on remote systems. My first thought was to use cURL for uploading since Bash does not have libraries like LWP for perl or urllib2 for python.
This approach failed miserably as Django did not seem to receive any files. Of course I tested my app using LWP, urllib2 and a browser form in which case the files were received as expected. After some researching and header tracing I found a quick solution: Curl is sending a HTTP Header 'Expect: 100-continue' which seems to break the server side response. See alse discussions on the Drupal site: http://drupal.org/node/434336 and discussions on http://pear.php.net/bugs/bug.php?id=15937 Instructing Curl to send an empty 'Expect' header 'fixes' the problem. Instead of using: curl -F data=@<filename goes here> -F submit=go http://<my submit url> i'm now using: curl -H 'Expect:' -F data=@<filename goes here> -F submit=go http://<my submit url> FYI: I tested this with the development server and Apache2 with WSGI,Django v 1.1 and trunk. It would be nice to find out if other server setups suffer from this 'problem' (lighttpd also seems to have problems with the 100-continue header. ) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
