htDig & ASP
"JL Martin" <[email protected]> Mon, 31 Jul 2006 18:44:07 -0700
| Newsgroups | gmane.comp.web.htdig.devel |
|---|---|
| Message-ID | <000d01c6b50b$fab3e880$6500a8c0@laptop> |
This is a multi-part message in MIME format. --===============0045475414== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01C6B4D1.4E2749C0" This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C6B4D1.4E2749C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, My hosting company (Telus) claims that htDig cannot index websites that = make use of ASP (they use version 3.1.6 and it worked in the past).=20 Here's an excerpt of their email ..... ....To summarize, the results that HtDig would receive from a site using = a server side scripting language could easily be ambiguous if not = meaningless. There really is no solution for this, as we cannot predict = what a developer might chose to code or how they might choose the make = the site work. The best that can be done is to realize that HtDig is a = good tool for static (html) websites. Unfortunately, as a result of it's = design and implementation, HtDig does not handle dynamically composed = websites very well or in a consistant manner. Any truth to this? Would upgrading to v3.2 resolve this (scripting) = issue? JL Martin ------=_NextPart_000_000A_01C6B4D1.4E2749C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1555" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>My hosting company (Telus) claims that = htDig cannot=20 index websites that make use of ASP (they use version 3.1.6 and it = worked in the=20 past). </FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Here's an excerpt of their email = .....</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV>....To summarize, the results that HtDig would receive from a site = using a=20 server side scripting language could easily be ambiguous if not = meaningless.=20 There really is no solution for this, as we cannot predict what a = developer=20 might chose to code or how they might choose the make the site work. The = best=20 that can be done is to realize that HtDig is a good tool for static = (html)=20 websites. Unfortunately, as a result of it's design and implementation, = HtDig=20 does not handle dynamically composed websites very well or in a = consistant=20 manner.</DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV>Any truth to this? Would upgrading to v3.2 resolve this = (scripting)=20 issue?</DIV> <DIV> </DIV> <DIV>JL Martin </DIV></BODY></HTML> ------=_NextPart_000_000A_01C6B4D1.4E2749C0-- --===============0045475414== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 --===============0045475414== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ht://Dig Developer mailing list: [email protected] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev --===============0045475414==--