While I appreciate that your intentions are not malicious and that you may well be within the terms of Google's service, I would very much prefer to avoid the potential issues altogether by not working around Google's technical limitations.
For experimenting with HttpClient I'd suggest you just pick a different URL - http://jakarta.apache.org would be a good one. If you do come across this problem or ones like it at other sites where the terms of service are less risky then we can certainly help you work how to get HttpClient to access the site. You'll find in the list archives that we've helped quite a number of people get HttpClient to work with sites that for some reason pose technical problems (usually because of their lack of standards compliance).
Regards,
Adrian Sutton.
On 12/07/2004, at 11:36 AM, Vincent Chain wrote:
Well, I view this as a technical question. I have no intention to use the code for automated querying and this is for my experiment of the HttpClient. Google happens to be the URL i choose. There could be another host that does similar things as google, but does not enforce similar terms. And the issue would still be there right? I am asking a technical question here, but your points are taken.
Thanks
---------------------------------------------- Intencha "tomorrow's technology today" Ph: 38478913 0422236329 Suite 8/29 Oatland Crescent Holland Park West 4121 Australia QLD www.intencha.com
PGP.sig
Description: This is a digitally signed message part
