Is it SSL? And for Chrome 16 users? If so, it's because of http://code.google.com/p/cherokee/issues/detail?id=1284
I've had to change webserver on a production host already because of that "fun" little problem :( -Mikael 2011/12/20 David Mohl <[email protected]> > Hey ! > First of all, i'm not quite sure if this is the right place for my > problem. Tho it's only cheorkee related. > > For about 1 weeks i'm getting a django error when trying to access my page > via post. The page is embedded in facebooks app-canvas. Means facebook > posts some data every time someone accesses the page. > > The problem occurs only in chrome as far as i can tell. > The handler itself is a simple uwsgi handler, using the following command: > "/usr/local/bin/uwsgi -s 127.0.0.1:58547 -x > /var/www/apps/myapp/uwsgi.xml" > > Stack Trace: > (...) > File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/wsgi.py", > line 210, in _get_post > self._load_post_and_files() > > File "/usr/local/lib/python2.7/dist-packages/django/http/__init__.py", > line 289, in _load_post_and_files > self._post, self._files = QueryDict(self.raw_post_data, > encoding=self._encoding), MultiValueDict() > > File "/usr/local/lib/python2.7/dist-packages/django/http/__init__.py", > line 249, in _get_raw_post_data > self._raw_post_data = self.read(content_length) > > File "/usr/local/lib/python2.7/dist-packages/django/http/__init__.py", > line 301, in read > return self._stream.read(*args, **kwargs) > > IOError: error waiting for wsgi.input data > > > UWSGI Output: > 'uwsgi.node': 'prismriver', > 'uwsgi.version': '0.9.9.2', > 'wsgi.errors': <open file 'wsgi_input', mode 'w' at 0x271f9c0>, > 'wsgi.file_wrapper': <built-in function uwsgi_sendfile>, > 'wsgi.input': <uwsgi._Input object at 0x2213120>, > > Tried to change some permission (because of the mode "w"), restarting the > server, messing around with uwsgi settings but didn't really help. > > Am i the only one having this problem? > It's kind of critial because the application is not usable for chrome > users anymore. > The problem occured someday all of a sudden. I didn't change anything on > the server settings (as far as i can remember). > > Any solutions on that? > Could the chrome 16 release last week be the problem? > > > Regards, > David > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
