ABEND dump #4
HTTP2 little surprise, Prometheus, culture vs strategy, and how to produce and learn at the same time
It’s been a while since the last ABEND dump. Want to check the previous issue? Read it here: ABEND dump #3
Thanks for reading Bit Maybe Wise! Subscribe for free to receive new posts and support my work.
This is more of a surprise than a rant, but, who would think that HTTP/2 would require headers to be exchanged all in lowercase when it has been indifferent up to now?!
According to the RFC section 8.1.2:
A request or response containing uppercase header field names MUST be treated as malformed (Section 22.214.171.124).
How did I stumble upon that? Like almost everything in life, many things happen by accident, and it was not different in this case. Last December I was playing with the prometheus/client_ruby, and decided to raise a pull request to fix an example when rack started shouting at me—surprise surprise—about the Content-Type header having uppercased letters, which lead me to another pull request to fix it.
So folks, be mindful from now on when dealing with your HTTP headers in your clients and servers.
Don’t do a ridiculously excellent job. That would take way more work and way more time.
A pretty good job, communicated well, is usually more valuable to the company than the best work of their best engineers.
Culture is the set of habits that allows a group of people to cooperate by assumption rather than by negotiation. Based on that definition, culture is not what we say, but what we do without asking.
A nice documentary about how Prometheus was born.
Subscribe for free to receive new posts.