https://issues.apache.org/bugzilla/show_bug.cgi?id=56041
--- Comment #1 from Erik Pearson <[email protected]> --- I've made a first pass, adding a configuration parameter SessionRefreshExpiry. This config can be set directly in a config file, or set via an If config, triggered on a request header field. I tested with a header field named "X-Session-Refresh-Expiry". Both direct config and via If behave as expected. I have another couple of changes to sessions that I need for my current project. One has been submitted in bugzilla as an enhancement (need to have cookie with "session" lifetime), and another not submitted yet (need "hard lifetime" of session -- the session may not live longer than this time limit.) Is it better to submit these as additional patches or as one unified patch? They involve the same set of files or at least overlap -- I don't know enough about svn to determine how difficult it is to manage multiple patches as the codebase is progressively modified without checkin... -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
