
nginx-sticky-module - issue #31
nginx-sticky module uses "Max-Age" directive instead of "Expires" to set cookie expiration
What steps will reproduce the problem? 1. check http headers returned by nginx with nginx-sticky-module-1.1 and "expires" parameter set for the sticky backend
What is the expected output? What do you see instead? Expected: Set-Cookie:route=foo; Domain=bar; Expires=date Got: Set-Cookie:route=foo; Domain=bar; Max-Age=seconds
What version of the product are you using? On what operating system? nginx-sticky-module-1.1
Please provide any additional information below. Internet Explorer <9 doesn't understand Max-Age. Expires should be used instead, as it's understood by all browsers
Patch is provided
- nginx_sticky_module.patch 1.84KB
Comment #1
Posted on Mar 5, 2014 by Helpful Bearthe module has been forked, patches will be included; see
Comment #2
Posted on Jun 30, 2014 by Happy LionThis project is now over and it's been forked to https://bitbucket.org/nginx-goodies/nginx-sticky-module-ng/overview
Status: WontFix
Labels:
Type-Defect
Priority-Medium