Good to know, thanks for posting this. On Feb 25, 2011 10:31 AM, "Ad" <[email protected]> wrote: > For anyone googling for this problem this issue was that I didn't have > > BrowserMatch "MSIE [2-6]" \ > nokeepalive ssl-unclean-shutdown \ > downgrade-1.0 force-response-1.0 > # MSIE 7 and newer should be able to use keepalive > BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown > > in my virtualhost. > > Thanks, > Adam > > On Feb 17, 3:16 pm, Graham Dumpleton <[email protected]> > wrote: >> On 17 February 2011 20:54, Ad <[email protected]> wrote: >> >> > I am running 2.2.16, this is my dpkg output. Could you post a >> > reference to the issue so I can look into it further? >> >> Not at the moment. My belief that SSL issues were fixed in one of the >> Apache versions around 2.2.16 or earlier was based on comments a long >> time ago in the Apache httpd developers list. Not sure what the >> description may have been that appeared in Apache release notes. >> >> Anyway, believe that 2.2.16 and later should be fine. So, since you >> are using 2.2.16 wouldn't be what I was potentially thinking about. >> >> Either way, the specific message you are seeing is due to an error in >> the Apache input filter chain and connection handler somewhere and >> mod_ssl and other stuff will be a part of that. In other words, pretty >> well out of the hands of mod_wsgi and due to the input filters and not >> mod_wsgi itself. >> >> So, not sure I got much insight on it at the moment. >> >> Graham >> >> > dpkg root@carboncloud:~# dpkg -l | grep apache >> > ii apache2 2.2.16-1ubuntu3.1 >> >> > Thanks, >> > Adam >> >> > On Feb 17, 1:56 am, Graham Dumpleton <[email protected]> >> > wrote: >> >> What version of Apache are you using. Some slightly older Apache 2.2.X >> >> versions had issues with SSL which may have resulted in this. Don't >> >> remember what version issues were addressed in. Think you may be fine >> >> if using Apache 2.2.16 or newer. >> >> >> Graham >> >> >> On 17 February 2011 02:21, Ad <[email protected]> wrote: >> >> >> > Hi there, >> >> >> > I'm not sure where the right place to ask this is so I hope you don't >> >> > mind me asking here. I have a django view which is calling >> >> > request.raw_post_data and getting an IOError. So the traceback looks >> >> > like: >> >> >> > IOError at /api1/bulk/ >> >> >> > request data read error >> >> >> > # /var/www/carboncloud.com/fp3/django-trunk/django/http/__init__.pyin >> >> > _get_raw_post_data >> >> > self._raw_post_data = self.read(content_length) >> >> >> > # /var/www/carboncloud.com/fp3/django-trunk/django/http/__init__.pyin >> >> > read >> >> > return self._stream.read(*args, **kwargs) >> >> >> > I believe this is happening because apache is timing out. From the >> >> > apache error log: >> >> >> > [Wed Feb 16 17:11:10 2011] [error] [client 86.24.194.171] (70007)The >> >> > timeout specified has expired: mod_wsgi (pid=26792): Unable to get >> >> > bucket brigade for request., referer:https://.../ >> >> >> > Now to me this looks like the client is simply leaving a tcp >> >> > connection up and not sending any data. However - the client is >> >> > actually receiving the response to this request and an error dialog is >> >> > showing up on the client side. So clearly the connection is still up. >> >> >> > Platform information: >> >> >> > Ubuntu maverick >> >> > Apache version 2.2.16-1ubuntu3.1 >> >> > libapache2-mod-wsgi 3.2-2 >> >> > Django 1.2 >> >> >> > The connection is an SSL connection. >> >> > mod_wsgi is in daemon mode >> >> > Apache timeout is 300 seconds >> >> >> > Thanks for any help, >> >> > Adam >> >> >> > -- >> >> > 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. >
-- 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.
