4.2. Document submission using HTML Forms

It is possible to write to a CouchDB document directly from an HTML form by using a document update function. Here’s how:

4.2.1. The HTML form

First, write an HTML form. Here’s a simple “Contact Us” form excerpt:

  1. <form action="/dbname/_design/ddocname/_update/contactform" method="post">
  2. <div>
  3. <label for="name">Name:</label>
  4. <input type="text" id="name" name="name" />
  5. </div>
  6. <div>
  7. <label for="mail">Email:</label>
  8. <input type="text" id="mail" name="email" />
  9. </div>
  10. <div>
  11. <label for="msg">Message:</label>
  12. <textarea id="msg" name="message"></textarea>
  13. </div>
  14. </form>

Customize the /dbname/_design/ddocname/_update/contactform portion of the form action URL to reflect the exact path to your database, design document and update function (see below).

As CouchDB no longer recommends the use of CouchDB-hosted web applications , you may want to use a reverse proxy to expose CouchDB as a subdirectory of your web application. If so, add that prefix to the action destination in the form.

Another option is to alter CouchDB’s CORS settings and use a cross-domain POST. Be sure you understand all security implications before doing this!

4.2.2. The update function

Then, write an update function. This is the server-side JavaScript function that will receive the POST-ed data.

The first argument to the function will be the document that is being processed (if it exists). Because we are using POST and not PUT, this should be empty in our scenario - but we should check to be sure. The POST-ed data will be passed as the second parameter to the function, along with any query parameters and the full request headers.

Here’s a sample handler that extracts the form data, generates a document _id based on the email address and timestamp, and saves the document. It then returns a JSON success response back to the browser.

  1. function(doc, req) {
  2. if (doc) {
  3. return [doc, toJSON({"error": "request already filed"})]
  4. }
  5. if !(req.form && req.form.email) {
  6. return [null, toJSON({"error": "incomplete form"})]
  7. }
  8. var date = new Date()
  9. var newdoc = req.form
  10. newdoc._id = req.form.email + "_" + date.toISOString()
  11. return [newdoc, toJSON({"success":"ok"})]
  12. }

Place the above function in your design document under the updates key.

Note that this function does not attempt any sort of input validation or sanitization. That is best handled by a validate document update function instead. (A “VDU” will validate any document written to the database, not just those that use your update function.)

If the first element passed to return is a document, the HTTP response headers will include X-Couch-Id, the _id value for the newly created document, and X-Couch-Update-NewRev, the _rev value for the newly created document. This is handy if your client-side code wants to access or update the document in a future call.

4.2.3. Example output

Here’s the worked sample above, using curl to simulate the form POST.

  1. $ curl -X PUT localhost:5984/testdb/_design/myddoc -d '{ "updates": { "contactform": "function(doc, req) { ... }" } }'
  2. {"ok":true,"id":"_design/myddoc","rev":"1-2a2b0951fcaf7287817573b03bba02ed"}
  3. $ curl --data "name=Lin&email=lin@example.com&message=I Love CouchDB" http://localhost:5984/testdb/_design/myddoc/_update/contactform
  4. * Trying 127.0.0.1...
  5. * TCP_NODELAY set
  6. * Connected to localhost (127.0.0.1) port 5984 (#1)
  7. > POST /testdb/_design/myddoc/_update/contactform HTTP/1.1
  8. > Host: localhost:5984
  9. > User-Agent: curl/7.59.0
  10. > Accept: */*
  11. > Content-Length: 53
  12. > Content-Type: application/x-www-form-urlencoded
  13. >
  14. * upload completely sent off: 53 out of 53 bytes
  15. < HTTP/1.1 201 Created
  16. < Content-Length: 16
  17. < Content-Type: text/html; charset=utf-8
  18. < Date: Thu, 05 Apr 2018 19:56:42 GMT
  19. < Server: CouchDB/2.2.0-948a1311c (Erlang OTP/19)
  20. < X-Couch-Id: lin%40example.com_2018-04-05T19:51:22.278Z
  21. < X-Couch-Request-ID: 03a5f4fbe0
  22. < X-Couch-Update-NewRev: 1-34483732407fcc6cfc5b60ace48b9da9
  23. < X-CouchDB-Body-Time: 0
  24. <
  25. * Connection #1 to host localhost left intact
  26. {"success":"ok"}
  27. $ curl http://localhost:5984/testdb/lin\@example.com_2018-04-05T19:51:22.278Z
  28. {"_id":"lin@example.com_2018-04-05T19:51:22.278Z","_rev":"1-34483732407fcc6cfc5b60ace48b9da9","name":"Lin","email":"lin@example.com","message":"I Love CouchDB"}