All, thanks for the suggestions. I do think it was an interrupted upload. Marco
On Tue, May 26, 2015 at 12:23 PM, Jonathan Vanasco <jonat...@findmeon.com> wrote: > It's been a long time since I've used Apache, but I think this might be a > variation of why I left that architecture. > > I recall that if you run mod_wsgi (or mod_python, or mod_perl, or mod_php) > on port 80, you could trigger timeout errors from slow connections or > cancelled requests. The fix was to run vanilla apache, or nginx, on port > 80 and then proxy back to your dynamic server (apache+mod_wsgi, gunicorn, > uwsgi, etc). The vanilla apache/nginx buffers the request/repsonse, so > your dynamic backend doesn't get tied up with pending timeouts or dropped > connections, and errors like this don't happen. > > That might not be what's going on – it's been a while since I saw errors > like this – but I think that might be the issue. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "pylons-discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/pylons-discuss/qNkhiMScHZ8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > pylons-discuss+unsubscr...@googlegroups.com. > To post to this group, send email to pylons-discuss@googlegroups.com. > Visit this group at http://groups.google.com/group/pylons-discuss. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
