You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've Googled a bit and found this: https://groups.google.com/forum/#!topic/modwsgi/ycwTB7wQz_8 you are seeing the messages because you are using the write() callback and not catching the IOError and aborting the request cleanly. [...] Note that write() is not considered best practice and you should try and return an iterable from WSGI application instead.
Anyone has experience in that?
The text was updated successfully, but these errors were encountered:
I'm not familiar with this code but it might just be clients closing the connection but that error not being handled in the middleware. How about we just catch and ignore this exception right there? Would you mind trying that and submitting a PR?
We decided to close old issues that are not actively worked on so that we can focus our effort and attention on issues affecting the current versions of CKAN.
If this issue is still affecting the version of CKAN you're working with now, please feel free to comment or reopen the issue.
If you do reopen this issue, please update it with new details. One reason it might not have been resolved in the past is that it wasn't clear how a contributor could address the issue.
CKAN Version if known (or site URL)
2.3.5
Please describe the expected behaviour
No errors in the apache log.
Please describe the actual behaviour
An error is thrown quite often, mostly for the tracking requests:
What steps can be taken to reproduce the issue?
It's not easy to reproduce
Diagnosis
In current CKAN it's this line.
I've Googled a bit and found this: https://groups.google.com/forum/#!topic/modwsgi/ycwTB7wQz_8
you are seeing the messages because you are using the write() callback and not catching the IOError and aborting the request cleanly. [...] Note that write() is not considered best practice and you should try and return an iterable from WSGI application instead.
Anyone has experience in that?
The text was updated successfully, but these errors were encountered: