Monitoring forms without side effects

HTTP result from a HTTP GET request to our demonstration form, without the response body
  • creates a new instance of that form behind the scenes
  • puts that instance’s id in a browser cookie so thereafter we know which form they’re using
  • logs an event

HTTP verbs to the rescue

So, if requesting the form just to see if it’s running isn’t ideal, what should we do instead? It turns out there’s a mechanism in HTTP that has been designed for precisely this:

HTTP result from a HTTP HEAD request to our demonstration form

Want to know more?

Come have a look around https://uxforms.com, follow UX Forms on twitter, or email us at hello@uxforms.com and see how we can make your forms better, together.

--

--

An enterprise-ready cloud platform for webform development. See our website for more: https://uxforms.com

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
UX Forms

UX Forms

An enterprise-ready cloud platform for webform development. See our website for more: https://uxforms.com