Joe McIlvain wrote:
> We work on an IoT-oriented web service that uses Unicorn. One of our
> requirements is to support HTTP/1.0 for low-complexity devices.
>
> We've noticed that HTTP/1.0 requests to Unicorn always get HTTP/1.1
> responses, which is invalid behaviour for the HTTP/1.0 protocol.
We work on an IoT-oriented web service that uses Unicorn. One of our
requirements is to support HTTP/1.0 for low-complexity devices.
We've noticed that HTTP/1.0 requests to Unicorn always get HTTP/1.1
responses, which is invalid behaviour for the HTTP/1.0 protocol.
Sure enough, looking through t
We work on an IoT-oriented web service that uses Unicorn. One of our
requirements is to support HTTP/1.0 for low-complexity devices.
We've noticed that HTTP/1.0 requests to Unicorn always get HTTP/1.1
responses, which is invalid behaviour for the HTTP/1.0 protocol.
Sure enough, looking through t
Brilliant, this will make it super easy to write a Prometheus
exporter, will post here once I am done.
On Tue, Nov 1, 2016 at 10:36 AM, Eric Wong wrote:
> Sam Saffron wrote:
>> Hi Eric / everyone :)
>>
>> I would like to start graphing how long our master process spends
>> waiting for worker pro