curl-users
Re: Reading a router (dumpfile blocked)
Date: Thu, 09 Feb 2006 15:11:48 -0500
Since the dumpfile I enclosed (should have known better!) was blocked, here
is the contents:
== Info: About to connect() to 192.168.102.1 port 80
== Info: Trying 192.168.102.1... == Info: connected
== Info: Connected to 192.168.102.1 (192.168.102.1) port 80
=> Send header, 162 bytes (0xa2)
0000: 47 45 54 20 2f 20 48 54 54 50 2f 31 2e 31 0d 0a GET / HTTP/1.1..
0010: 55 73 65 72 2d 41 67 65 6e 74 3a 20 63 75 72 6c User-Agent: curl
0020: 2f 37 2e 31 33 2e 31 20 28 70 6f 77 65 72 70 63 /7.13.1 (powerpc
0030: 2d 61 70 70 6c 65 2d 64 61 72 77 69 6e 38 2e 30 -apple-darwin8.0
0040: 29 20 6c 69 62 63 75 72 6c 2f 37 2e 31 33 2e 31 ) libcurl/7.13.1
0050: 20 4f 70 65 6e 53 53 4c 2f 30 2e 39 2e 37 69 20 OpenSSL/0.9.7i
0060: 7a 6c 69 62 2f 31 2e 32 2e 33 0d 0a 48 6f 73 74 zlib/1.2.3..Host
0070: 3a 20 31 39 32 2e 31 36 38 2e 31 30 32 2e 31 0d : 192.168.102.1.
0080: 0a 50 72 61 67 6d 61 3a 20 6e 6f 2d 63 61 63 68 .Pragma: no-cach
0090: 65 0d 0a 41 63 63 65 70 74 3a 20 2a 2f 2a 0d 0a e..Accept: */*..
00a0: 0d 0a ..
<= Recv header, 17 bytes (0x11)
0000: 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d HTTP/1.1 200 OK.
0010: 0a .
<= Recv header, 25 bytes (0x19)
0000: 53 65 72 76 65 72 3a 20 52 61 70 69 64 20 4c 6f Server: Rapid Lo
0010: 67 69 63 2f 31 2e 31 0d 0a gic/1.1..
<= Recv header, 19 bytes (0x13)
0000: 4d 49 4d 45 2d 76 65 72 73 69 6f 6e 3a 20 31 2e MIME-version: 1.
0010: 30 0d 0a 0..
<= Recv header, 36 bytes (0x24)
0000: 44 61 74 65 3a 20 53 61 74 20 4a 61 6e 20 20 33 Date: Sat Jan 3
0010: 20 31 32 3a 32 37 3a 33 34 20 31 39 37 30 20 47 12:27:34 1970 G
0020: 4d 54 0d 0a MT..
<= Recv header, 25 bytes (0x19)
0000: 43 6f 6e 74 65 6e 74 2d 54 79 70 65 3a 20 74 65 Content-Type: te
0010: 78 74 2f 68 74 6d 6c 0d 0a xt/html..
<= Recv header, 28 bytes (0x1c)
0000: 54 72 61 6e 73 66 65 72 2d 45 6e 63 6f 64 69 6e Transfer-Encodin
0010: 67 3a 20 63 68 75 6e 6b 65 64 0d 0a g: chunked..
<= Recv data, 232 bytes (0xe8)
0000: 3c 68 74 6d 6c 3e 0d 0a 20 20 3c 74 69 74 6c 65 <html>.. <title
0010: 3e 4d 6f 74 6f 72 6f 6c 61 20 54 65 72 6d 69 6e >Motorola Termin
0020: 61 6c 20 41 64 61 70 74 65 72 20 53 74 61 74 75 al Adapter Statu
0030: 73 3c 2f 74 69 74 6c 65 3e 0d 0a 20 20 3c 66 72 s</title>.. <fr
0040: 61 6d 65 73 65 74 20 63 6f 6c 73 3d 22 31 39 35 ameset cols="195
0050: 2c 2a 22 20 66 72 61 6d 65 62 6f 72 64 65 72 3d ,*" frameborder=
0060: 4e 4f 20 62 6f 72 64 65 72 3d 30 20 66 72 61 6d NO border=0 fram
0070: 65 73 70 61 63 69 6e 67 3d 30 3e 0d 0a 20 20 20 espacing=0>..
0080: 20 3c 66 72 61 6d 65 20 73 72 63 3d 22 73 69 64 <frame src="sid
0090: 65 2e 68 74 6d 6c 22 20 73 63 72 6f 6c 6c 69 6e e.html" scrollin
00a0: 67 3d 4e 4f 3e 0d 0a 20 20 20 20 3c 66 72 61 6d g=NO>.. <fram
00b0: 65 20 73 72 63 3d 22 73 74 61 72 74 75 70 64 61 e src="startupda
00c0: 74 61 2e 68 74 6d 6c 22 3e 0d 0a 20 20 3c 2f 66 ta.html">.. </f
00d0: 72 61 6d 65 73 65 74 3e 0d 0a 3c 2f 68 74 6d 6c rameset>..</html
00e0: 3e 0d 0a 30 0d 0a 0d 0a >..0....
== Info: Received problem 2 in the chunky parser
== Info: Closing connection #0
=Alan R.
On 2/9/06 2:21 PM, "Daniel Stenberg" <daniel_at_haxx.se> wrote:
> This is interesting. I figure Firefox and similar browsers can view this fine?
> Any chance you can --trace dumpfile and show us that? It might reveal what the
> problem with the chunked stream is.
Received on 2006-02-09