I've found out I can update apache and stay on the media temple UOP, so I'll do that shortly and test again. Thanks
On Apr 21, 3:19 pm, Jake <[email protected]> wrote: > I've setup the WSGI debugging app, and when I try to get a page it > shows me the headers. However when I submit the upload form I get > firefox saying "The connection to the server was reset while the page > was loading." The same as I usually get, but Django usually emails me > an exception and traceback. > > In firebug (without the WSGI debugging app in place) When I copy > response or request headers, I get nothing. > > I hope that is useful information. I'm at a loss to explain it. > > As for apache, I'm reluctant to upgrade because of the Media Temple > Update Option Program*. However I'll look into it now, if my apache is > that old, then perhaps the UOP is not that useful. > > *http://kb.mediatemple.net/questions/97/FAQ:+Update+Option+Program+ > (UOP) > > On Apr 21, 10:58 am, Graham Dumpleton <[email protected]> > wrote: > > > > > > > On 21 April 2010 08:51, Jake <[email protected]> wrote: > > > > I'm getting a request data read error when trying to upload files to > > > the Django admin interface. > > > > Files under about 150k work, but bigger files always fail and almost > > > always at around 200k. The Exception I get is below. > > > > File "/usr/lib/python2.4/site-packages/django/http/ > > > multipartparser.py", line 405, in read > > > return self._file.read(num_bytes) > > > IOError: request data read error > > > > I'm running python 2.4, django 1.1, apache 2.2.3, mod_wsgi 2.8, on > > > CentOS (a media temple DV server) > > > I've tried Chrome and Firefox on Windows and Firefox on Mac - Same > > > results. > > > I've tried wsgi daemon mode and embedded > > > I can upload to other sites so I don't think it's my connection. > > > Locally it's fine (Django development server) > > > > Everything I've found on this error says it's a mod_python issue and > > > that changing to mod_wsgi will fix it, but I am running mod_wsgi. > > > Can anyone help? > > > Use recipe in: > > > http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Displaying_... > > > to capture the WSGI environment as passed to the WSGI application and > > post it for analysis. > > > Use FireBug in Firefox to capture the headers sent by the browser for > > the upload and post it for analysis. > > > Try installing most recent Apache 2.2.X instead of the old version you > > are using in case it is all because of using old Apache. Especially do > > this as mostly pointless exercise debugging it if not using most up to > > date Apache. > > > Graham > > > -- > > You received this message because you are subscribed to the Google Groups > > "modwsgi" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/modwsgi?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/modwsgi?hl=en. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
