Will McCutchen

So, at a high level, I'm in favor of some combination of a) adding a new, more explicit and hopefully discoverable `/chunked` endpoint b) making the `Transfer-Encoding: chunked` behavior of...

Yeah, I'm really torn on this. While making httpbingo.org a drop-in replacement for (at least the most common/basic functionality of) httpbin.org would be great, that particular pattern is particularly ugly...

> and then > > ``` > GET /get?foo[]=12&foo[]=23 > ``` > > Should got > > ```json > { > foo: ["12", "23"], > } > ``` Minor note:...

Yep! This is gonna take a bit more digging on my end, as expected client and server behavior in the face of a 100 Continue response, and how we might...

@prune998 👋 hi! I think some intentionally malformed endpoints make sense, I’d definitely welcome a PR for that! On the other hand, I’m not really interested in pulling in all...

@Integralist go for it! A pile of new endpoints have been added recently by @saurabh-hirani: - /bearer added in #21 - /json added in #20 - /base64 added in #18...

The behavior of the original httpbin service used to be that it would return a single string for single-valued headers or a list of strings for multi-valued headers, and I...

Note: The old method for request signing (based on a per-upstream shared secret) is documented here: https://github.com/buzzfeed/sso/blob/master/docs/sso_config.md#request-signing Those docs should probably be deprecated or removed in favor of the new...

> To start, generating an appropriate keypair for sso_proxy to use for signing requests is as simple as > > ```shell > openssl genrsa -out priv.out 2048 > ``` Turns...

Minor suggestion based on past frustrations automating the deployment of software versioned as suggested above: Consider splitting the application version and any other metadata onto separate lines, for easier consumption...