I believe that the surprise would come from it not meaning "get the f* out." Which makes perfect sense to me - GTFO has a meaning, and re-backronyming it can only harm understanding of the standard. Also consider non-native English speakers, which is really important when developing international standards.

The fact that someone suggested a corresponding "HTTP TITS" should set off at least minor warning bells that "HTTP GTFO" is not a good thing to put in the standard. I certainly don't want to see HTTP LOL (Long Overdue Listen), HTTP WAT (Wireless Ask Transmit), etc.

Humor is great, but good standards are better.