HTTP/s parse C library and algorithm development environment.
Go to file
2024-09-08 21:41:17 +02:00
streecmp@ca1293aa8f fix: remove cluttered state machine code 2024-09-03 21:07:52 +02:00
.gitignore repo: implement tests and response parsing 2024-09-04 20:36:31 +02:00
.gitmodules feat: implement parsing of headers 2024-09-03 00:03:32 +02:00
Makefile repo: implement tests and response parsing 2024-09-04 20:36:31 +02:00
parslib.c feat: store parsed results fully in heap 2024-09-08 21:41:17 +02:00
parslib.h feat: store parsed results fully in heap 2024-09-08 21:41:17 +02:00
README repo: implement tests and response parsing 2024-09-04 20:36:31 +02:00
strings.c fix: remove cluttered state machine code 2024-09-03 21:07:52 +02:00
test.c feat: store parsed results fully in heap 2024-09-08 21:41:17 +02:00

+=============+
|   parslib   |
+=============+

    HTTP/s parse C library and algorithm development
    environment for - my proxy library - proxlib.

    RES: github.com/tinyproxy/tinyproxy
    RES: github.com/nginx/nginx
    RES: git.0xdeadbeer.xyz/0xdeadbeer/proxlib

TECHNICALS

    int initres(void);
    void fretres(void);
    int readlin(char **buff, char **buff_lim);
    int parshfield(char **offset, int len, /* out */ struct point *hentries);
    int parstitle(char *offset, int len, /* out */ struct httitle *titl);
    int parsme(char **buff, /* out */ struct httpars *pars);
    void printfpars(struct httpars *pars);

    Library is designed to follow source input unaltering. 
    Which suggests, that it does not directly alter the input
    data or strings while giving users the ability to 
    store the parsed information (struct httpars) either on the 
    stack or heap.

LEAKS 

    LEAKS file contains the most recent valgrind 
    memory leaks dump ran on a test program.

TODO 
    
    * integrations with tinyproxy..?