[wildcard-comments] Sitefinder and Web Services
I have just written up the results of my experiments on how leading SOAP-based web service stacks behave when sitefinder is changing their failure modes:
The core summary is that sitefinder turns what could be a comprehensible error, "Unknown Host" into something more obscure such as System.InvalidOperationException (.NET SOAP stack) or (302)Found (on Apache Axis).
Obscure client-side errors result in support calls and other expenses incurred while trying to track down configuration defects.
I therefore advocate leaving the sitefinder service off indefinitely. DNS is the wrong place to be making changes in the infrastructure not just to support one protocol -HTTP- but one use case -a human at the end of the wire.