<<<
Chronological Index
>>> <<<
Thread Index
>>>
[wildcard-comments] Wildcard System degrades possibility for automatic link checking validity
- To: <wildcard-comments@xxxxxxxxx>
- Subject: [wildcard-comments] Wildcard System degrades possibility for automatic link checking validity
- From: "Kirk Potter" <Kirk.Potter@xxxxxxxxxxxxxx>
- Date: Tue, 30 Sep 2003 12:42:49 +0100
- Importance: Normal
- Sender: owner-wildcard-comments@xxxxxxxxx
Dear Sirs,
Content Management Systems (CMS) often provide link checking
functionality for external links provided in a content managed site.
This would normally be done by making an HTTP request to the given page
(if appropriate) and checking the HTTP response code. In the case of
uninstantiated .com or .net domains this check is easy to perform and
validate until Verisign made their change.
It now means that CMSs now need to look at specific headers to detect
the verisign site finder site specifically and this presentw issues for
the future if they change the site in any way.
What was once zero maintenance now has a maintenance element that was
never invisaged nor expected.
We and I am sure many other CMS providers would strongly object to the
wildcard response to uninstantiated domains and move that it should be
removed.
Best Regards,
Kirk Potter
R&D Director
C(2) Software
Tayside Software Centre
Technology Park
Dundee
DD2 1TY
T 01382 598450
F 01382 598449
E kirk.potter@xxxxxxxxxxxxxx
W www.c2software.com
This e-mail, its content and any files transmitted with it are intended
solely for the addressee(s) and may be legally privileged and/or
confidential. Access by any other party is unauthorised without the
express
written permission of the sender. If you have received this e-mail in
error
you may not copy or use the contents, attachments or information in any
way.
Please destroy it and contact the sender via e-mail return. This e-mail
has
been prepared using information believed by the author to be reliable
and
accurate, but C(2) Software makes no warranty as to accuracy or
completeness. In particular C(2) Software does not accept responsibility
for changes made to this e-mail after it was sent. Any opinions
expressed in
this document are those of the author and do not necessarily reflect the
opinions of C(2) Software.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|