Skip to main content

Handling multipart/form-data with NanoHTTPD

I am in the process of reviving an old project from 2014 that I never finished because of other work commitments. In that time, bitrot has set in, the Android API has moved on and all in all, the home-brewed HTTP server I wrote using SocketServer and the org.apache libraries had to go!

I looked around, found a couple of contenders and after much time decided to go with NanoHTTPD because it is lean, small and fits in exactly two files. The main server is in one file `NanoHTTPD.java`and there is another file called `ServerRunner.java` which manages instances of running servers.

The others

The other project I looked at is this one: https://github.com/koush/AndroidAsync
which led me a merry dance and I just couldn't figure out how get the POST data I had uploaded. I spent a few days really digging at it with Wire Shark too to make sure the data was going up. It was. Whatever... I had used it via a gradle dependency entry but I dropped it and went back to NanoHTTPD.

For me, NanoHTTPD is short, sharp and to the point. Whilst other offerings make it easy to set up URL routing with regex expressions and callbacks and things, NanoHTTPD leave all that down to you and your creativity! I prefer that anyway.

POST and multipart/form-data

With all the other things it does, NanoHTTPD does them well, offers simple but efficient helper functions here and there but the one thing it currently doesn't have is the ability to stream the incoming data to your application. Instead, it uploads the entire file into the local device, normally ending up somewhere under the `/sdcard/` folder. Typically it creates files like this, this is `adb shell` listing the `/sdcard` folder after uploading a simple JPEG image:
----rwxr-x system   sdcard_rw    38546 2016-06-03 13:32 NanoHTTPD--1954269476
Thankfully it also cleans up after it has finished... when your serve() method has completed, it will automatically delete any files that it creates which is quite handy!

Getting your data

So... here is my custom serve() function, I've posted the complete method. I've written my own handler factory code that gives back an instance of my ICmdHandler interface and that's why it is so short. In order to use NanoHTTPD you have to create a subclass of it and then override a single function like this:

  @Override
  public Response serve(IHTTPSession session) throws IOException, ResponseException
  {
    Map<String, String> fileList = null;
    Method method = session.getMethod();

    if (NanoHTTPD.Method.POST.equals(method) || NanoHTTPD.Method.PUT.equals(method)) {
      fileList = new HashMap<>();
      session.parseBody(fileList);
    }

    ICmdHandler handler = EmCmdBase.handlerFor(app, session, fileList);
    return handler.execute(session, this.app);
  }

Using the file data

Once you have called `session.parseBody()`, which could take a while according to the number and size of files uploaded, you can use the usual classes to read them. On return, `fileList` will contain one entry per uploaded file, the first entry is the name associated with the upload, for example, the following `curl` command:
curl -F stuff=@my_data.txt http://device_ip:port/<app-url>
...will result in a `multipart/form-data` uploaded to the device, and then `fileList` will be of size 1 and the key will be "file" and the value will be the unique name given to it by NanoHTTPD. Here is a variable expansion from AndroidStudio of a single uploaded file:


Remember that the default NanoHTTP file manager will these files for you.

So, there you go... a simple and effective way to get POST data using NanoHTTPD. It's a really really clever and nice project, please check it out!

NanoHTTPD GitHub page


Comments

Popular posts from this blog

PHP and Lisp: multiple-value-bind (MVB)

This is another article in my attempts to find new ways of looking at PHP and making it less of a chore to type in all that code. As much as I love PHP I hate wasting keystrokes. More typing is more errors is more grief. Being an off and on user of Lisp, although not as much as I used to, one of the things that I always liked in Lisp was the ability to be able to return multiple values from a function at once using (values) and then marry that with (multiple-value-bind) to create convenient named bindings for whatever you were about to do. I recently found myself wanting to return a couple of values from a helper function and I just didn't want to go to the trouble of having to type all those character required to create an array with keys for the two values and then I remembered MVB and a little light went on in my head! If somebody else has already done this then I apologise up front but it was new to me and I haven't seen it anywhere else so this could be a first! ...

Angular.JS ... absolutely awesome BUT...

Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaagh! Sort the documentation soon please!  More soon, I really do like it though. :)

Cross platform development with Scheme

Just a quick note about something I recently found whilst trying not to buy MOCL… http://www.lambdanative.org/ LambdaNative is developed and maintained by the Pediatric Anethesia Research Team (PART) and the Electical and Computer Engineering in Medicine (ECEM) group at the University of British Columbia (UBC). I have spent a week or two evaluating it and accidentally contributed a pull request that got merged and one that didn’t and I have to say that, for what it offers, it is awesomely good. Having personally spent many hours with it now, I do not yet think it is ready for mainstream development for a few reasons. I don’t mean that it a bad way either. What I mean is that the language, Scheme, is not really that widely known and as such it probably won’t break out into the public arena any time yet. That’s a real shame because I think that they have achieved an amazing thing; total abstraction of the underlying platform with a really powerful, underestimated language. ...