-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> Interesting. Something like: wget --user-agent=AvantGo > --referer=http://avantgo.com http://space.com/syn/avantgo/ No, space.com is actually doing something a bit smarter than that, in fact. They appear to be looking at REMOTE_ADDR, and determining if the request comes from an allowed set of addresses in the AvantGo.com netblock. If not, the request is denied. There's a way around it, but it's not an easy path, mangling the packet itself, but you'll never see the data coming back, since a forged REMOTE_ADDR would send the response to the request off to the address you're forging, i.e. AvantGo somewhere. The other option is to hack a root DNS server to point that IP and netblock back to you. I don't recommend this approach, however =) There's a third approach, but I'm not going to discuss it on a public mailing list out in the open, where members and employees of AvantGo are most-certainly subscribed and listening. d. perldoc -qa.j | perl -lpe '($_)=m("(.*)")' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.1.92 (GNU/Linux) iD8DBQE9j5urkRQERnB1rkoRAklKAKDGnCBvjWagd253WXB5OWb34oZ4xQCgrAsq rOvDxNZc4BcJRJrLWxWMv6k= =NrLV -----END PGP SIGNATURE----- _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
