> 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?
> 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 change where they
> eithe
