Fix a couple of Ajax related path issues

  - Include context path when generating page specific JS
  - Include context path when making Ajax requests
  - Fix Ajax path matching (previously renderVersion was being set to
    "ajax")

fixes #1591 
Just to confirm my assumptions here... the session cookie is still specific
to the actual domain you're communicating with, isn't it? and this is why
the comet session ID is also provided in the URL?


On Mon, Aug 4, 2014 at 2:08 AM, Antonio Salazar Cardozo <
notifications@github.com> wrote:

> In web/webkit/src/main/resources/toserve/lift.js:
>
> > @@ -73,6 +73,7 @@
> >          window.location.href = "/";
> >        },
> >        cometServer: "",
> > +      ajaxServer: "",
>
> To clarify a little regarding cometServer: that's designed to make it so
> you can avoid per-domain connection limits by using wildcard DNS and
> pointing each page to its own random subdomain. You can always make a
> different domain for anything work, all you have to do is have the DNS set
> up properly and a server that will accept connections at the other domain
> and forward them to the application as needed.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/lift/framework/pull/1597/files#r15737516>.
>