Thread: Starting download file (requests)?

Originally Posted by kaszynek

HTTP/1.1 200 OK
P3P: CP="ALL DSP COR CURa ADMa DEVa TAIa PSAa PSDa IVAa IVDa CONa TELa OUR STP UNI NAV STA PRE"
Date: Tue, 02 Jun 2009 11:20:59 GMT
Connection: close
Accept-Ranges: bytes
Content-Type: text/html; charset=ISO-8859-1
Cache-Control: no-cache
Content-Encoding: gzip
Content-Length: 2658

What i have to do to start downloading this file?? im using recive function but server dont send file to me, i think i have to do something first

You just did. The file is not sent to you in as a .gz file, it is sent as raw data in an internet packet. That is the header. The rest of that packet (the 2658 bytes of gobbledy-gook that followed) is the gzip file. You have strip the packet header/inet wrapper off and write that raw binary data (using fwrite) into a file. Then call it "myfile.gz" and voila! you downloaded a gzip file.

Originally Posted by bithub

There is probably a problem with the way you are calling recv().

Only if you have the message you posted but there was no 2658 bytes attached to it...which would be impossible. The server *did* send it, it *was* part of that packet.

Again, you have to dissemble the packet. The server does not send a file, any file, as a discrete unit. It all arrives as a stream of data.

Originally Posted by MK27

You just did. The file is not sent to you in as a .gz file, it is sent as raw data in an internet packet. That is the header. The rest of that packet (the 2658 bytes of gobbledy-gook that followed) is the gzip file. You have strip the packet header/inet wrapper off and write that raw binary data (using fwrite) into a file. Then call it "myfile.gz" and voila! you downloaded a gzip file.

He's not downloading a gzip file. He's attempting to download a .rar archive, that happens to be sent gzip encoded by the server. Really, it'll be more like myfile.rar.gz. However, notice the content-type: text/html - either the server is not sending back a rar file at all, and is sending back HTML, or the server is sending the wrong Content-Type. (Probably the former.)

Originally Posted by MK27

Only if you have the message you posted but there was no 2658 bytes attached to it...which would be impossible. The server *did* send it, it *was* part of that packet.

Again, you have to dissemble the packet. The server does not send a file, any file, as a discrete unit. It all arrives as a stream of data.

No. The server sends a stream of data. From the client & servers point of view, packets are not involved. Whether the OP is actually getting this data into whatever buffer he may have, we cannot tell here, as he hasn't posted any code. The likely answer is that if he is, he is doing so by luck.
If the OP would post his code invovling recv(), as bithub requested, we would be able to know a lot more about what is actually going on.

Originally Posted by bithub

It was most certaintly not part of that packet considering the Content-Length is greater than a MTU.

While yes, it is irrelevant. The OP may have captured all 2-3 thousand bytes in a single recv(). One recv() != one TCP/IP packet.