Web debug proxy roundup

If you are developing Flash sites that talk to a backend system via XML or flash remoting, you need a web debug proxy.

A web debug proxy sits between your machine and the internet, and displays any HTTP traffic that passes between the two. This is invaluable for debugging Flash RIAs and data driven sites, by showing you exactly what data is being loaded into the browser. Some web proxies also offer bandwidth throttling which simulates a slow internet connection, and is useful for testing flash preloaders. There are currently 3 web debug proxies that are commonly used:

  • Fiddler. Windows only (requires .NET Framework v1.1). IE only. Free. Does not offer bandwidth throttling. Allows you to manipulate the data being loaded on the fly.
  • Charles. PC/Mac/Linux (requires Java 1.2). Firefox/IE compatible. 30 day trial, $50 for a license. Offers bandwidth throttling. Full featured but can be a little slow to load.
  • ServiceCapture. Windows only (requires Java 1.4.2). Firefox/IE compatible. 15 day trial, $35 for a license. Offers bandwidth throttling. Works well with flash remoting data, fast loading, clean interface. (Disclaimer: ServiceCapture is developed by my workmate Kevin Langdon.)

2 Responses

  1. Chris Hiester says:
    September 21, 2005 at 12:51 am

    Interesting resources. I have also used the NetConnection Debugger that comes with Flash Remoting. Good old Ethereal (http://www.ethereal.com/) works for this purpose as well.

  2. Adam Platti says:
    September 21, 2005 at 1:49 am

    Fiddler is not IE only. It runs on port 8888 so any browser that supports HTTP proxies can connect to it. It does automatically attach and detach to IE, however. Other browsers will have to manually turn on and off this proxy setting.