CookieOptions doesn't have MaxAge property

[themacguffinman]

Even though SetCookieHeaderValue supports it, CookieOptions does not have a MaxAge property which means that there is no way to append cookies with a Max-Age.

[Tratcher]

Interesting, you're the first to ask for it.

Note you can use SetCookieHeaderValue and add the header directly.

[themacguffinman]

Thanks @Tratcher.

For anyone reading this, here's a quick extension method that uses SetCookieHeaderValue directly:

public static class HttpExtensions
{
    public static void AppendCookie(this IHeaderDictionary headers, SetCookieHeaderValue cookie)
    {
        headers[HeaderNames.SetCookie] = StringValues.Concat(headers[HeaderNames.SetCookie], cookie.ToString());
    }
}

Usage:

Response.Headers.AppendCookie(new SetCookieHeaderValue("usid", String.Empty)
{
    Path = "/",
    HttpOnly = true,
    MaxAge = TimeSpan.Zero,
});

Remember to Uri.EscapeDataString() the cookie name and value if it is potentially unsafe.

Now that I think about it though, why isn't this the official method of adding cookies? CookieOptions seems a little redundant.

[muratg]

Thanks for the recommendation. We'll consider post 1.1. Feel free to send a PR :)

[jkotalik]

We may also have to modify CookieBuilder.cs to accommodate this change.