> On Feb 14, 2018, at 1:08 PM, jonathan vanasco wrote:
>
> also, it might be worth adding to the “ThinkToKnow” docs that if you’re doing
> anything with oAuth against twitter or Facebook, you should increase the
> buffer size. one (or more) platforms had some recent
we have a few HTTP endpoints that have very large request payloads (headers +
query string). They’re all oAuth endpoints coming in from 3rd parties, with a
bunch of header data and a super long query string.
the quick fix was to double buffer-size to 8192
is this the best approach?
also,
Sorry, I didn't received your reply. No, it is not in the spam :)
Anyway this is the vassal log:
**
*** Starting uWSGI 2.0.16 (64bit) on [Wed Feb 14 11:40:01 2018] ***
compiled with version: 6.3.0 20170516 on 14
Il 14/02/2018 10:18, Luigi Cirillo ha scritto:
Sometimes (not always but often) it happens one of the two vassals is
never ready to accept requests. Following the logs, in this case
djangoapp_uwsgi.ini doesn't accept requests.
Do you know how I can obtain info about where uwsgi get stuck?
I'd
Sometimes (not always but often) it happens one of the two vassals is
never ready to accept requests. Following the logs, in this case
djangoapp_uwsgi.ini doesn't accept requests.
Do you know how I can obtain info about where uwsgi get stuck?
;uWSGI instance configuration
[uwsgi]
ini =