Rev 4168 | Rev 4242 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 4168 | hidnplayr | 1 | |
| 4221 | hidnplayr | 2 | *url = pointer to ASCIIZ URL |
| 4168 | hidnplayr | 3 | *add_header = pointer to ASCIIZ additional header parameters, or null for none. |
| 4221 | hidnplayr | 4 | Initiates a HTTP connection, using 'GET' method. |
| 4168 | hidnplayr | 5 | - returns 0 on error, identifier otherwise. |
| 6 | |||
| 7 | |||
| 4221 | hidnplayr | 8 | *url = pointer to ASCIIZ URL |
| 4168 | hidnplayr | 9 | *add_header = pointer to ASCIIZ additional header parameters, or null for none. |
| 4221 | hidnplayr | 10 | Initiate a HTTP connection, using 'HEAD' method. |
| 4168 | hidnplayr | 11 | - returns 0 on error, identifier otherwise |
| 12 | |||
| 13 | |||
| 4221 | hidnplayr | 14 | *url = pointer to ASCIIZ URL |
| 4168 | hidnplayr | 15 | *add_header = pointer to ASCIIZ additional header parameters, or null for none. |
| 4221 | hidnplayr | 16 | *content-type = pointer to ASCIIZ string containing content type. |
| 4168 | hidnplayr | 17 | content-length = length of the content (in bytes). |
| 18 | Initiate a HTTP connection, using 'POST' method. |
||
| 19 | The content itself must be send to the socket (which you can find in the structure), |
||
| 20 | using system function 75, 6. |
||
| 21 | - returns 0 on error, identifier otherwise |
||
| 22 | |||
| 23 | |||
| 24 | identifier = identifier which one of the previous functions returned |
||
| 25 | This procedure will handle all incoming data for a connection and place it in the buffer. |
||
| 26 | As long as the procedure expects more data, -1 is returned and the procedure must be called again. |
||
| 27 | - When transfer is done, the procedure will return 0. |
||
| 28 | |||
| 29 | |||
| 30 | This structure is defined in http.inc (and not copied here because it might still change.) |
||
| 31 | The identifier used by the functions is actually a pointer to this structure. |
||
| 32 | In the dword named .flags, the library will set various bit-flags indicating the status of the process. |
||
| 33 | (When a transfer is done, one should check these bit-flags to find out if the transfer was error-free.) |
||
| 34 | All received data is placed at the end of this structure, including HTTP headers. |
||
| 35 | The dword .status contains the status code received from the server (e.g. 200 for OK). |
||
| 36 | In header_length you'll find the length of the header as soon as it has been received. |
||
| 37 | In content_length you'll find the length of the content (not counting headers). |
||
| 38 | In content_received, you'll find the number of bytes already received (not counting headers). |
||
| 39 |