Hi all, I'm trying to get a .site file for Yahoo groups working reliably. At the moment I've got it 'mostly' working but there are a couple of recurring problems.
The most annoying one is that Yahoo groups occasionally redirects a request for a group message to an ad page, which includes a link to get to the real story. The snag is (I think) that the 'real' story URL and the original request URL (which got redirected) are the same, so sitescooper caches the ad page and never scoops the actual message, even on subsequent scoops which stand a good chance of not being redirected. What I need (ideally) is a way to get Sitescooper to treat the redirect target differently from the 'real' story page for caching purposes (tricky, I know!). Ideally I'd also like to be able to spot the redirect and retry the HTTP GET or to follow the link from the ad page to the real story. A simpler but less satisfactory alternative would be to add a construct to the site file (and the necessary SiteScooper logic to handle it) along the lines of 'StoryURL' or 'URLProcess' called 'StoryRedirectURL' or 'RedirectProcess' so that the site file can at least abort the scoop of a page which gets redirected to an ad so that it doesnt get cached and the next scoop has a good chance of fetching the real story. I'm happy to have a go at doing the mods for the second (simpler) suggestion myself but I'd appreciate any comments on either suggestion - especially if someone can come up with a way to solve the problem without changing Sitescooper. I'll put the other problem in another thread. Cheers, Andy _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. _______________________________________________ Sitescooper-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sitescooper-talk
