Yes, columns use text sorting rules by default but you can change that by binding the column using FiddlerScript.

Click Rules, Customize Rules.

Just inside the existing code block class Handlers { add the following code:


public BindUIColumn("OrigID", 50 /*width*/, 1 /*order*/, true/*sortNumerically*/)
static function ShowOriginalID(oS: Session): String {
return oS["x-OriginalSessionID"];
}

Thanks for your feedback, Eric.

It makes sense to not restore the sessionIds (to not create mixups) but rather keep then as a separate field (such as x-OriginalSessionID) .

The issue is that here too, it isn't currently possible to sort by this field properly: The sorting is by string comparison and not by numerical value. (see attached screen shot).

Perhaps the fix should be just to sort this field (and perhaps other numerical ones) properly.

The problem here is that reloading the original Session ids works poorly if there's any other traffic either being captured or in the Web Sessions list. Having duplicate or out-of-order Session IDs is problematic.

For Fiddler *Viewer* instances, where there is no captured traffic (in theory), it might be reasonable to try to restore the original Session IDs for a loading capture IIF there are no other sessions in the Web Sessions list. But as soon as you try to load two captures, everything falls apart.

As you noted, the original Session ID is typically shown in the Comments column. Beyond that, you can type the following in the QuickExec box under the Web Sessions list:

   prefs set fiddler.saz.ReloadIDAsFlag true

and hit Enter.

After you do that, each time you load a SAZ file, the original Session ID is stored in a new flag on the Session, named x-OriginalSessionID. You can add a new column to Fiddler's Web Sessions list to show that column (just right-click the column headers).