ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 5831] New: Exporting HTTP traffic with GET queries fails i

Date: Thu, 14 Apr 2011 09:13:55 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5831

           Summary: Exporting HTTP traffic with GET queries fails in
                    Windows
           Product: Wireshark
           Version: 1.4.4
          Platform: All
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: glenn@xxxxxxxx


Build Information:
Version 1.4.4 (SVN Rev 36110 from /trunk-1.4)

Compiled (64-bit) with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, without
SMI, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
Gcrypt 1.4.5, without Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 
1 2011), with AirPcap.

Running on Windows XP Professional x64 Edition Service Pack 2, build 3790, with
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version
1.0 branch 1_0_rel0b (20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022

--
File->Export->Objects->HTTP on a capture containing HTTP traffic with query
parameters (http://url?query) fails in Windows with the error "Some files could
not be saved."  It's trying to use URL components as the pathname, but question
marks aren't allowed in Windows filenames.  It also doesn't filter other
invalid characters, like colons.

The only painful workaround I've found is to save each file one at a time, to
enter a filename manually.  I'd suggest allowing the saved URL to be
URL-encoded.

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