Whew

You probably got to this page from here.

On May 13, 2002, in a particular newsgroup a guy named Andrew asked a question

("microsoft.public.frontpage.client"news:2d5201c1fa8b
$8a78df60$9be62ecf@tkmsftngxa03,
so you could look it up),

and a certified expert on the subject named Mike responded with the following, which I quote verbatim:

Usually a permissions issue see if this helps.

http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/vsentpro/ht
ml/veconsettingwebserverpermissions.asp

url may wrap

HTH
Mike

• Forget about the fact Mike should have said, "It is usually."
• Forget about the fact the sickeningly overused term "issue" is here misleading.
• Forget about the fact he should have said, "See whether this helps."
• Forget about the fact this is a run-on sentence.
• Forget about the fact he should have said, "The url."
• Forget about the fact he should have said, "The URL."
• Forget about the fact he should have ended the sentence with a period.
• Forget about the fact I have no idea what "HTH" means, nor, I suspect, do 50% of the thousands of other visitors to this extremely popular newsgroup.

No, what's interesting, though hardly surprising, is that where Mike says, "url may wrap," he means the exact opposite.  He means not that the URL is permitted to wrap but rather that it might but may not.

And it continues.  A day later I responded in the newsgroup as follows:

Mike, on a new Web page I'm creating [this very page] I'd like to quote your response to Andrew in this thread.  I have use for exactly what you typed.  May I have your permission?  Thanks. -- Johnny

Mike's response -- I swear to God -- was as follows:

What "use" could you possibly have to quote that?