https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1671
--- Comment #4 from Stephen Fisher <steve@xxxxxxxxxxxxxxxxxx> 2010-10-14 18:23:34 MDT ---
(In reply to comment #3)
> 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.
I looked into this when I first wrote the export object http feature and it
turned out to be harder than you would think to test for invalid characters. I
figured there would be an automatic function you could call so Windows (where
most of the problems lie) would come back and tell you if it was a valid file
name or not. Then it turns out that different versions of Windows have
different functions and capabilities based on the underlying file system (such
as NTFS vs FAT32). A hard-coded list of what we don't think would work such as
the MSDN link you gave would probably be our best bet to cut down on most of
the problems.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
