Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 1671] Export HTTP > All - System Appears Hung (but isn't)

Date: Wed, 13 Oct 2010 07:39:37 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1671

--- Comment #3 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2010-10-13 07:39:25 PDT ---
Just a follow-up ...

Of the files that were not saved that were not duplicates, except for one file,
they all contained invalid characters in their filename, e.g., '\', '?', '|',
etc.  Those characters are not allowed.  (See
http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx)

The one file that wasn't saved for another reason was the one in packet #1229,
which began with "ESPN+Front+Page&search.keywords...".  That file wasn't saved
because its name exceeded the maximum allowable.

So, it looks to me that if Wireshark is to be able to save files of these
types, then at a minimum, it would have to scrub the filenames more or less as
follows:

1) Look for invalid characters in the filename and replace them with
"something", remove them altogether, or just truncate the filename at the first
invalid character ... unless of course the first invalid character is the very
first character, in which case "something" would have to be used instead.

2) Limit the filename to the max length allowed, which will vary depending on
the path to where the file is to be saved

3) Account for duplicate filenames somehow.

The adverse side-affect of all 3 of these is that the original object filename
will not be preserved.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.