uniuri | Go package uniuri generates random strings good for use | Runtime Evironment library

"Random" behavior is hard to debug and reason about without a reproducible example.

Some errors and notes regarding your handler.

1. If the COOKIE_EXPIRE env var is not an integer, your handler sends back an error response and does not return. Note that you can't set other headers (including cookies) after you write anything to the response (http.Error() does write to the response).

2. If the COOKIE_EXPIRE is an integer but is negative or 0, the cookie expiration (expire variable) will point to the past and will result in the cookie being deleted in the browser.

3. If cookie name is invalid (COOKIE_NAME env var), the cookie may be silently discarded (as per the doc of http.SetCookie()).

4. Since you set Secure to true, note that the cookie may be set in the browser, but it will not be included (sent) when insecure (HTTP) requests are made to your server.

5. If executing the template fails (tmpl.ExecuteTemplate()), some of the response may already be committed, so you can't send another response (not even http.Error()). You either have to execute the template directed into a buffer, and if it succeeds, then send it; or send it directly to the response, but if it fails, you can't make corrections afterwards (best you can do is log the error for later inspection).