- Fri Mar 06, 2015 12:38 pm
#11468
@Sprite_tm making stream a flag makes sense and makes space for other useful things. I just added support for multipart form encoded data which gets us towards being able to upload a new espfs image and write it to flash directly without having to reflash the module over serial. It seems to be working pretty well, though I needed to extract the boundary delimiter from the header in the header parsing stage and store it for later.
I've also brought out the HTTP verb so that it can be accessed by the cgi handler which means you can have a particular URL respond differently to GET or POST requests. I've tried to keep commits isolated into single commits where they can be.
@prozac there's now an embedded form which lets you choose a file to upload and then parses it - take a look at the updateWeb function in cgi.c for this. If you have any files you could share on writing to the flash memory that would be useful. If you want to play with what I've done so far, it's in this branch:
https://github.com/bjpirt/esphttpd/tree/streaming
I've also brought out the HTTP verb so that it can be accessed by the cgi handler which means you can have a particular URL respond differently to GET or POST requests. I've tried to keep commits isolated into single commits where they can be.
@prozac there's now an embedded form which lets you choose a file to upload and then parses it - take a look at the updateWeb function in cgi.c for this. If you have any files you could share on writing to the flash memory that would be useful. If you want to play with what I've done so far, it's in this branch:
https://github.com/bjpirt/esphttpd/tree/streaming
