Do some link rot cleanup while in here.

Fix X-UA-Device-force cookie

Not required

Change resp.response to resp.reason as this is passed to vcl_synth
Change set of  resp.response to resp.http.response (varnish 4)
Setting resp.status before using resp.reason resets resp.reason to "OK" and results in A-UA-Device-force cooking being set to "OK". Swap ordering to avoid this.

Update scheme

Minor updates

Update OpenDDR URL

Changed elif to elsif.

I am not a VCL expert but it seems like the 'elif' on line 45 should be 'elsif'.

As requested in issue #19.

Currently only googlebot mobile.

Based on work by "redhat-raptor" on Github.

My Makefile-foo isn't developed enough to figure out how to get TESTS
expanded after the initial vtc file generation has happened.

For now hack around it by splitting into two targets, and run the
generating one manually first.

Make the test set be run from the top level instead, and
add an initial travis-ci.org configuration.

As pointed out by Alex Gonzalez Lacasa.

This is an example, we can afford a few extra line feeds
so it is easier to read.

I think up to a hundred test cases should be sufficient here.

These three tests really did test the same, merge them to
save test run overhead.

No changes to the ruleset itself.

Also clean up/out some formatting mistakes from two years ago.

Update README.rst - capitalization

Fix inconsistent capitalization.

Added a warning concerning X-UA-Device

Commented the X-UA-Device, as we found out, that Google could interpret this wrong. Google marked our site as "hacked" without any real hack going on. We removed only that X-UA header, getting marked as clean again. It seems that Google is interpreting this as crafted content only for SEs (X-UA-Device:bot) as used by Viagra, Cialis SE hacks on servers (showing nothing to the browser, but spamming SE index with spam for bots)