Table of Contents Previous Next 


Case Study: Google Web Accelerator


  • client-side proxy, a whopping cache
  • leverages Google's amazing server farms
  • Exposed pervasive HTTP Abuse in minutes
  • Developers have been misusing HTTP semantics e.g. using hyperlinks (GET) to DELETE and/or cause side effects (POST, PUT)
  • Idempotency - GET should not have side-effects
  • GWA pre-fetched links on pages (smart spider)
  • People Lost Data = Tears = Pain = $$$
  • I'm Sorry I can't kiss and make it better
  • Frameworks using HTTP should be better to mitigate these risks
  • Still, developers need to internalize the web architecture