I remember someone saying that good test of HTTP-knowledge is to browse internet using telnet. That may be a bit too cumbersome now. At the time, some websites were hand-written HTML so it was a bit more pleasant to read. On the other hand, interacting with REST-API should be rather trivial. Only potential issue is that HTTPS doesn't work but there is an alternative.
Web developer should be familiar with tools like curl or httpie. That kind of tools are essential time to time when debugging things. I don't think you can use those tools effectively without having some grasp of the underlying protocols (TCP and HTTP).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I remember someone saying that good test of HTTP-knowledge is to browse internet using
telnet. That may be a bit too cumbersome now. At the time, some websites were hand-written HTML so it was a bit more pleasant to read. On the other hand, interacting with REST-API should be rather trivial. Only potential issue is that HTTPS doesn't work but there is an alternative.Web developer should be familiar with tools like
curlor httpie. That kind of tools are essential time to time when debugging things. I don't think you can use those tools effectively without having some grasp of the underlying protocols (TCP and HTTP).