Fiddler – Web Debugging Proxy & Monitoring Tool

I recently found an Network Traffic Monitoring tool for HTTP requests. Previously i used Ethereal (an ultimate tool). Fiddler is equally good for http traffic. It also provides many other features. Read more @

Fiddler is a Web Debugging Proxy which logs all HTTP(S) traffic between your computer and the Internet. Fiddler allows you to inspect all HTTP(S) traffic, set breakpoints, and "fiddle" with incoming or outgoing data. Fiddler includes a powerful event-based scripting subsystem, and can be extended using any .NET language.

Fiddler is freeware and can debug traffic from virtually any application, including Internet Explorer, Mozilla Firefox, Opera, and thousands more.

download icon Download Fiddler…

Other links:

Code Review Tools (free)

When the developers had written the codes, we need the Code review Tools to find the BUG out. So, we can review the style, logic,……., and find the problems ,and modify the code. The Code Review is the key in coding. There are five Open-source Code Review tools below:

1. Review board :
Review board is a tool based on web,which was primarily designed to those who like to use Python Programming Language and Django .Review could help to trace the change of the pending code and make the Code-Review more easily and simply. Although Review board was originally designed to the VMware, it could be universal. At present, it can support such management soft wares as SVN,CVS, Perforce, Git ,Bazaar, Mercurial.Yahoo is one of the review-board users.
“Review board has changed the way to review code, which could be a mentor to the programmer .When you access the site, all of the codes are reviewed by the Review board tools.”These words you will see :”We’re great fans of your work!” – Yahoo! Web Search”.
2. Codestrike:
Codestrike is also a Web-based tool, which was chiefly used to review the online code the GCI-Perl script supported. Traditional document reviews are supported, as well as reviewing diffs generated by an SCM (Source Code Management) system and plain unidiff patches. Codestriker could be integrated in CVS, Subversion, ClearCase, Perforce and Visual SourceSafe.
Codestriker is written in Perl, and runs on all of the major platforms and browsers, and is licensed under the GPL.
View an example code review:
3. Groogle
Groogle is a web based peer code review tool providing a range of features aimed at easing the code review process. Features include:
• Subversion integration, working against live repositories.
• Syntax highlighting for a wide variety of languages.
• Comparisons of entire repository trees to find added, removed and modified files and directories.
• Diffing of individual files and a graphical representation of modifications.
• E-mail notifications to notify review participants when a reviews status changes.
• Optional integration against a wide range of existing authentication mechanisms.

4.Rietveld: Code Review for Subversion, hosted on Google App Engine .It was based on Mondrian, which was similar to Review board. But it used django that was the most popular web development frame, and supported the Subversion. At present, All who used Google Code can use Rietveld and Python Subversion server, too.

5. JCR
JCR (or jcodereview as it’s known on Sourceforge) is a web application for performing and managing formal code reviews. It can be used for reviews of any type of source code, although it has some special smarts for reviewing Java projects. It has special features to make large-scale reviews not only practical but easy and fast. JCR is intended to assist:
• Reviewers. All changes to code are highlighted, and syntax highlighting works for most languages. Code extracts are shown for context when adding comments. If reviewing Java code, references to other classes within the file are clickable, so that you can drill into the detail if required. After review comments have been made, those comments can themselves be reviewed, and the required actions decided on and tracked
• Project owners. Review projects are easy to create and configure, and support (but don’t require) integration with your source code management (SCM) system
• Process bigots. Details of all comments are held in the database, along with any actions required, and whether they’ve been completed. Status reports can be viewed at any time, and also show how much review activity took place on each file (to make sure they were all reviewed)
• Architects and developers. As well as viewing the comments made for a project, it’s possible to see details of all review projects and comments for a specified file – good for finding code that would benefit from refactoring.
JCR is generally targeted at larger-scale and more formal code reviews than other review tools.


Testing with IE6, IE7 and IE8 on VirtualBox

Microsoft’s Virtual Hard Drives

Microsoft make a series of downloads available for web developers to ensure browser compatibility. Currently you can download IE6-8 on XP and IE7 on Vista. The good news is that they are also free so there is no need to buy a Windows license if all you want to do is browser test. The images generally expire at the end of each quarter but it is fairly trivial to download a new version.
Extracting the .exe

The downloads are available as .exe files so you will need to extract them first. On OSX I use Stuffit which extracts .exe files on the free version. Andrew Odri also has a write up on this and he recommends using The Unarchiver although this didn’t work for me.

On Ubuntu you can use Wine:
sudo apt-get install wine

Once installed you can use Wine to extract the exe:
wine /path/to/yourexe.exe
Get VirtualBox

Next download and install VirtualBox. On OSX you can download a .dmg file. On Ubuntu the following will install it for you:
sudo apt-get install virtualbox
Fixing Microsoft’s duplicate identifiers

The Microsoft images all share the same Hard Disk Identifier which means that VirtualBox will only let you add one of the hard drives to the Media Manager. So we need to fix that. Hat tip to Andrew Odri for documenting this.

For OSX Download Q and then for each vhds we need to convert it to a vdi. This will allow us to test in parallel. On OSX run:
/Applications/ convert -O raw -f vpc yourVHD.vhd RAWimage.raw
VBoxManage convertdd RAWImage.raw NewVDIImage.vdi

For Ubuntu get QEMU:
sudo apt-get install qemu

Once installed on Ubuntu you can then convert the .vhd to a .vdi
qemu-img convert -O raw -f vpc yourVHD.vhd RAWimage.raw
VBoxManage convertdd RAWImage.raw NewVDIImage.vdi
Fixing drivers

Once you have set up your Virtual Machine and booted you will see a blue screen of death. This is because we still need to install some drivers. When booting hold down F8 and boot into Safe Mode with Command Prompt. Cancel any prompts that come up and at the DOS prompt enter
cd \WINDOWS\system32\drivers
ren processr.sys processr.old

Restart the machine and then in the VirtualBox menu go to Devices > Install Guest Additions. Follow the prompts and install the additions. On Ubuntu I found I had to manually download the iso from the link supplied, then mount it in the machine settings before booting. Reboot when you are done.

Once rebooted at the DOS prompt type
D:\VBoxWindowsAdditions-x86.exe /extract /D=C:\Drivers

This will extract the VirtualBox drivers

Then within Windows do

* Start > Administrative Tools > Computer Management
* Select Device Manager.
* Select Batteries, Unknown Device -> Disable
* Select Network Adapters, Ethernet Controller -> Update Driver
* Select Yes, now and every time, click Next
* Select Install from a list or specific location, click Next
* Enter location “C:\Drivers\x86\Network\AMD”
* Click Finish

All done – repeat this method on the other vhds and you will then have a full IE6-8 testing suite that you can run side-by-side if you wish.

This article draws on knowledge gained from the following posts and I’m very grateful to the authors