I thought this had all died down, but at the recent ICANN meeting on the
topic, there was a little presentation by VeriSign that covered feedback
from their little field experiment . Page 25 is the core one for web
services, though pages 21-23 are mildly entertaining, particularly all
the places where the recommended workarounds are 'application patches'
and 'user education'. It'll be our apps and our users, I suspect.
Slide #26 says :-
Automated HTTP Tools
Issue: Automated processes using HTTP over TCP port 80 may
exhibit problems when encountering the Site Finder page
instead of a DNS Name Error response
Response: No reported occurrences
o The site includes a robots.txt file to prevent indexing
o Other types of automated tools are discouraged according
to BCP 56
Which means that (a) nobody complains and (b) you shouldn't be using
anything other than web browsers to talk HTTP on port 80.
Accordingly I have just written up the experiments I conducted while
sitefinder was live testing both Axis and .NET WSE 2.0 clients: both
failed with error messages that were definitely not consumer friendly.
The full paper is at ; I will send it to Matt Larson next week so
that he can't make the 'none reported' claim any more.
 Review of Technical Issues and VeriSign Response
 The Impact of Site Finder on Web Services