It's like a series of tubes. That's why SWE work involves so much plumbing and getting deep into all sorts of $#!+.
Also, React is not slow at displaying tables. If it’s slow, you can use plugins to hide cells which are not in the viewport.
(Old farts like me manage a billion records and display tables of 7k rows x 100 columns in a webpage in mere milliseconds, a joy that React developers will never understand. Why do you need more than 10 lines if you have pagination, they say).
They don't have to read RFCs in bed before sleep, but they should at least know the gist of what they contain.
Interview 0:
"I expect them to know the basics of HTTP and to be capable of referencing/digesting an RFC"
Interview 1:
"All devs should be up to speed on the mysterious world of character sets, encodings, Unicode, all that stuff"
Interview 2:
"Any real programmer can reverse a string in C without a buffer"
Interview 3:
"I expect anyone working with k8s to understand the cgroup fundamentals."
Interview 4:
"No really. What is html5?"
Are you doing something fancy with HTTP?
Overall I agree with your gate-keeping comment - that's how people interview/hire. I disagree that it "has no place" - if I'm hiring a mid-to-senior engineer that's web-capable I am 100% gate-keeping to make sure they have an intimate understanding of HTTP + are capable/comfortable reading RFCs.