PEAK XOOPS - Google Web Accelerator 
Google Web Accelerator
- You cannot open a new topic into this forum
- Guests cannot post into this forum
Previous post
-
Next post
|
Parent
-
Children.1
|
Posted on 2005/5/8 5:35
spiff
Posts: 2
Posts: 2
Hello GIJoe,
Posted a thread on the main Xoops site regarding Google Web Accelerator.
Outside of the hack provided by Ackbarr, could you enlighten us on how the Protector module handles these prefetch requests, and if anything needs to be done to prevent automated clicks from corrupting a Xoops site? Can I block an entire range using Protector (e.g. by entering 72.14.192.0-255)?
Thanks,
Eric
Posted a thread on the main Xoops site regarding Google Web Accelerator.
Outside of the hack provided by Ackbarr, could you enlighten us on how the Protector module handles these prefetch requests, and if anything needs to be done to prevent automated clicks from corrupting a Xoops site? Can I block an entire range using Protector (e.g. by entering 72.14.192.0-255)?
Thanks,
Eric
Votes:13
Average:5.38
GIJOE
Posts: 4110
Posts: 4110
hi spiff.
I've researched about GWA.
And I believe that it is necessary for XOOPS sites to protect from GWA.
Quote:If you know the IP range, the easiest way is using .htaccess. then set deny.
I've researched about GWA.
And I believe that it is necessary for XOOPS sites to protect from GWA.
Quote:
Outside of the hack provided by Ackbarr, could you enlighten us on how the Protector module handles these prefetch requests, and if anything needs to be done to prevent automated clicks from corrupting a Xoops site? Can I block an entire range using Protector (e.g. by entering 72.14.192.0-255)?
Votes:6
Average:10.00
Previous post
-
Next post
|
Parent
-
No child
|
Posted on 2005/5/12 18:47
spiff
Posts: 2
Posts: 2
Yes, it's probably more efficient to do it on the Apache/firewall side than on the PHP side.
Votes:0
Average:0.00
Login