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

The Coolest Shortest PHP Function I Will Ever Write

Having now released my own programming language, FELT , and learned a lot about this and that in the process I have of late, in the evenings, been struggling to reconcile my love of LISP and how simple FELT makes some PHP coding task leaner and meaner with the fact that I still have to use PHP for my day job. In my language, FELT , I have used the square brackets to define a "normal" array and curly braces to define a "key-value" array, mainly because this is identical to JSON format and anybody familiar with Javascript coding just won't have any issues getting to grips with that now will they! Let's take some simple examples of FELT code: (defvar simple-array [1 2 3 4]) (defvar simple-map {:name "Eric" :age 42 :occupation "Viking Hacker"}) When FELT has done its thing, we get the following PHP code, $simple_array = array(1, 2, 3, 4); $simple_map = array('name' => "Eric", 'age' => 42, ...

Using a RAM disk with Opera on OS X

Having recently configured AndroidStudio to use a RAM disk for Gradle, I thought I would look around and see if I can use the remaining space for Opera. This is essentially a reproduction of this fine page: http://www.ghacks.net/2010/10/20/how-to-change-the-opera-cache-directory/ That page does not deal with Macs though and after a little bit of experimentation I came up with this spell: open /Applications/Opera.app/ --args --disk-cache-dir=/Volumes/RamDisk/opera For the record, here is my Opera version: Make sure that the specified folder exists before starting Opera, if might automatically create the folder for you but I didn't bother to find out, I hate disappointment. And for the record, the way I create a RAM disk on my iMac, which is done automatically when I log in, is like this: diskutil erasevolume HFS+ "RamDisk" `hdiutil attach -nomount ram://4194304` The above line was courtesy of this YouTube video: Thanks to Bartech TV then! So, with Turbo m...