| Age | Commit message (Collapse) | Author | 
|---|
|  | on FreeBSD | 
|  |  | 
|  |  | 
|  | It is not compatible between linux and freebsd (different number of
parameters) | 
|  |  | 
|  |  | 
|  | TODO: needs refactoring | 
|  | This license is compatible with the GPL. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | Still open: Split the header/body parser, but this is more complicated,
so maybe some automated tests first. | 
|  | We can:
* skip HTTP status header
* read the HTTP headers
* find a boundary of multipart form data and if there was a boundary
  * parse further 'chunks', separated by this boundary, each with a HTTP
    header
All of that was tested with text fields and binary data. This server
implementation is insecure. Please do not use it for anything connected
to the internet. It is simple though and can serve local daemons.
TODO: callback to a parser function. | 
|  | Well-- If I had read the entire input stream into the buffer, I would
afterwards be able to change the buffer in memory and append \0 in
places, where a name/value pair exists and that would every second pair
a name and avoid many unnecessary memcpy. | 
|  | * threads removed for now, because that was unrelyable and sometimes the
  connection could not be established. Investigation why is pending.
* used openfd to open the socket, because working with a FILE structure
  is much more straight forward
* added several parsing functions down to the level of detail, so that
  every chunk of multipart form data can be processed individually. The
  header parsing of these parts is still missing though. | 
|  |  | 
|  |  |