Only if you plan for the horn to keep honking until you patch again, I figure. GET definitely should not produce a honking sound. GET is meant to not have side

Only if you plan for the horn to keep honking until you patch again, I figure. GET definitely should not produce a honking sound. GET is meant to not have side-effects. If the response to the GET were, say, a URL which refers to a usable honk (that could then be POSTed to) then it might sort of make sense. But, no, producing sound is i/o. This is bad design.