Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #2197
| From | Xavier Roche <xroche@free.fr.NOSPAM.invalid> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: HTTP POST for file upload |
| Date | 2013-06-05 19:51 +0200 |
| Organization | Nowhere Corp. |
| Message-ID | <kontr2$nln$1@news.httrack.net> (permalink) |
| References | <b19bg3FpriuU1@mid.individual.net> |
Le 05/06/2013 19:40, Josef Moellers a écrit : > content_length = 0; > content_length += fprintf(tmpfp, "\r\n"); /* This belongs to the > content */ No, this belongs to the HTTP headers. <http://www.ietf.org/rfc/rfc2616.txt> (...) 4 HTTP Message 4.1 Message Types (...) Request (section 5) and Response (section 6) messages use the generic message format of RFC 822 [9] for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header fields, and possibly a message-body.
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
HTTP POST for file upload Josef Moellers <josef.moellers@invalid.invalid> - 2013-06-05 19:40 +0200
Re: HTTP POST for file upload Xavier Roche <xroche@free.fr.NOSPAM.invalid> - 2013-06-05 19:51 +0200
Re: HTTP POST for file upload Richard Kettlewell <rjk@greenend.org.uk> - 2013-06-05 18:53 +0100
Re: HTTP POST for file upload Josef Moellers <josef.moellers@invalid.invalid> - 2013-06-06 21:26 +0200
Re: HTTP POST for file upload Jorgen Grahn <grahn+nntp@snipabacken.se> - 2013-06-06 21:51 +0000
csiph-web