Actions
Bug #8905
closedTake into account that Django development server is not powerful
Start date:
05/30/2018
Due date:
% Done:
0%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
It seems that a development server of Django 2 sometimes does not handle requests well like a production server. Instead it rejects them, breaks pipes, uploaded files, etc. Before we did not suffer from this issue so much, but now it happens often and we lose quite many verification results. Anyway we should not rely on any server and spend as much time as could be necessary to perform reliable and predictable communication.
Updated by Evgeny Novikov over 6 years ago
- Related to Feature #8729: Bridge does not work with Django 2.* added
Updated by Ilja Zakharov over 6 years ago
- Status changed from New to Resolved
Implemented directly in core-new-formats.
Updated by Evgeny Novikov over 6 years ago
- Related to Bug #8668: Connection error warnings can lead to task decision results misinterpretation added
Updated by Evgeny Novikov over 6 years ago
- Status changed from Resolved to Closed
Actions