HTTP server connectors influences the behavior of CookieSetting

[thboileau]

tested scenario:

• in a ServerResource, add a @post annotated method with the following cookie settings

    @Post
    public void login(String json) {
        getResponse().getCookieSettings().add(new CookieSetting(0, "a", "value", "/", null));
        getResponse().getCookieSettings().add(new CookieSetting(0, "b", "value", "/", getReference().getHostDomain()));
        getResponse().getCookieSettings().add(new CookieSetting(0, "c", "value"));
        getResponse().getCookieSettings().add(new CookieSetting(1, "d", "value", "/", null));
        getResponse().getCookieSettings().add(new CookieSetting(1, "e", "value", "/", getReference().getHostDomain()));
        getResponse().getCookieSettings().add(new CookieSetting(1, "f", "value"));
    }

• develop an application and run it using the internal connector, the Jetty one, the Simple, the Servlet one.
• according to the connector, some cookies are set, others don't
• the internal connector seems the most permissive one.