Re: Preventing Google Web Accelerator from prefetching

2005-11-19 Thread Richie Hindle
[Richie] >def process_request(self, request): >if 'prefetch' in request.META.get('HTTP_X_MOZ', '').lower(): >response = HttpResponseForbidden() >response['Vary'] = 'x-moz' >return response [Georg] > Actually that will break all vary-header handling

Re: Preventing Google Web Accelerator from prefetching

2005-11-19 Thread hugo
>> Secondly, there may be some things to consider with web caches. I >> think you should add a vary header to indicate that the response will >> vary depending on the value of the HTTP_X_MOZ header, or some such. > >Good point, thanks: > >def process_request(self, request): >if 'prefe

Re: Preventing Google Web Accelerator from prefetching

2005-11-19 Thread hugo
>behavior. GWA *only* issues GET requests, and if an app >modifies >data based on a GET, then the app should be considered >broken. Actually the problem goes deeper: GWA can crawl areas that normally can't be crawled, because they are behind logins. So GWS will hit pages that were never meant to

Re: Preventing Google Web Accelerator from prefetching

2005-11-18 Thread Eugene Lazutkin
Inline. "Richie Hindle" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > > [Luke] >> I know some people want to use links (i.e. HTTP GET requests) which >> have side effects, which is Bad. > > [Jacob] >> if an app modifies >> data based on a GET, then the app should be considered

Re: Preventing Google Web Accelerator from prefetching

2005-11-17 Thread Luke Plant
On Thu, 17 Nov 2005 00:21:29 + Richie Hindle wrote: > > > [Luke] > > I know some people want to use links (i.e. HTTP GET requests) which > > have side effects, which is Bad. > > [Jacob] > > if an app modifies > > data based on a GET, then the app should be considered broken. > > "Logout

Re: Preventing Google Web Accelerator from prefetching

2005-11-17 Thread Jeremy Dunck
On 11/17/05, Simon Willison <[EMAIL PROTECTED]> wrote: > HTTP purity is a nice ideal, but until the HTML form model contains > better support for calling HTTP verbs that reflect what you are > actually trying to do it just isn't practical in every case. It's > those edge cases that make GWA's beha

Re: Preventing Google Web Accelerator from prefetching

2005-11-17 Thread Simon Willison
On 16 Nov 2005, at 23:10, Jacob Kaplan-Moss wrote: However... the concept is. Developers shouldn't be blocking GWA; we should be programming web apps that conform to expected HTTP behavior. GWA *only* issues GET requests, and if an app modifies data based on a GET, then the app should b

Re: Preventing Google Web Accelerator from prefetching

2005-11-16 Thread Richie Hindle
[Luke] > I know some people want to use links (i.e. HTTP GET requests) which > have side effects, which is Bad. [Jacob] > if an app modifies > data based on a GET, then the app should be considered broken. "Logout" is often a link, like it or not. (Amazon, Gmail, Yahoo...) And yes, server r

Re: Preventing Google Web Accelerator from prefetching

2005-11-16 Thread Luke Plant
On Wed, 16 Nov 2005 22:16:23 + Richie Hindle wrote: > > Hi, > > I've written a small piece of middleware to prevent Google Web > Accelerator (or any other prefetching client) from prefetching URLs. Can I ask first of all why you are doing this? If you are trying to conserve your bandwidt

Re: Preventing Google Web Accelerator from prefetching

2005-11-16 Thread Jacob Kaplan-Moss
On Nov 16, 2005, at 4:16 PM, Richie Hindle wrote: I've written a small piece of middleware to prevent Google Web Accelerator (or any other prefetching client) from prefetching URLs. Since this is my first piece of middleware, I'd appreciate it if those more experienced than me could tell me