summaryrefslogtreecommitdiff
path: root/config/initializers/session_store.rb
Commit message (Collapse)AuthorAgeFilesLines
* Display and revoke active sessionsAlexis Reigel ( 🌴 may 2nd - may 9th 🌴 )2018-05-021-15/+11
|
* `current_application_settings` belongs on `Gitlab::CurrentSettings`Sean McGivern2017-08-311-2/+1
| | | | | | | | | | | | | | | | The initializers including this were doing so at the top level, so every object loaded after them had a `current_application_settings` method. However, if someone had rack-attack enabled (which was loaded before these initializers), it would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't have that method. To fix this: 1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need `Object.new.current_application_settings` to work. 2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it like that in several places. 3. Change the initializers to use that new form.
* Support multiple Redis instances based on queue typePaul Charlton2017-07-111-3/+3
|
* Update session cookie key name to be unique to instance in development31644-make-cookie-sessions-uniqueEric Eastwood2017-06-011-1/+7
| | | | Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/31644
* Deduplicated resque.yml loading from several placesGabriel Mazetto2016-08-041-2/+2
| | | | We will trust redis configuration params loading to Gitlab::RedisConfig.
* Enable Style/RedundantParentheses rubocop coprubocop/enable-redundant-parentheses-copGrzegorz Bizon2016-05-301-1/+1
| | | | See #17478
* Fix "remember me" sign in optionJacob Vosmaer2016-05-021-1/+1
|
* Redis configuration consistencyredis_config_consistencyValery Sizov2016-04-131-1/+1
|
* Add Gitlab::Redis connection poolJacob Vosmaer2016-04-041-1/+1
|
* Parse config/resque.yml in one place onlyJacob Vosmaer2016-03-091-1/+4
|
* Merge branch 'master' into reference-pipeline-and-cachingDouwe Maan2015-12-021-4/+5
|\
| * Rails update to 4.2.4Valery Sizov2015-11-251-2/+2
| |
| * Also fallback to a default value if none is set.session_expire_delay_cannot_be_nilMarin Jankovski2015-11-241-2/+2
| |
| * Maybe rescue session_expire_delay by setting a default value.Marin Jankovski2015-11-241-0/+1
| |
| * Disabling cache for test environmentValery Sizov2015-11-161-9/+11
| |
* | Disabling caching in test environment because it was causing issues with ↵Douwe Maan2015-10-221-9/+13
|/ | | | Markdown
* Merge branch 'master' into ci-and-ce-sitting-in-a-tree-k-i-s-s-i-n-gDmitriy Zaporozhets2015-09-111-1/+6
|\ | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
| * Fix reading session_expire_delay when application settings are not yet ↵Kamil Trzcinski2015-09-091-1/+6
| | | | | | | | created and migrations are not yet done
* | Groundwork for merging CI into CEDouwe Maan2015-08-251-1/+1
|/
* Ensure `session_expire_delay` field exists before accessing itrs-issue-1798Robert Speicher2015-06-131-4/+4
| | | | Closes #1798
* session_expire_seconds => session_expire_delaythemaze752015-06-101-2/+6
| | | | | delay is in seconds more legible code in session_store Added `GitLab restart required` help block to session_expire_delay
* Add session expiration delay configuration through UI applicationEric Maziade2015-06-051-1/+1
| | | settings
* Merge branch 'redis_settings'Dmitriy Zaporozhets2014-08-281-1/+1
|\ | | | | | | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> Conflicts: CHANGELOG
| * Store sessions in a Redis namespaceJacob Vosmaer2014-08-261-1/+1
| | | | | | | | This makes less of a mess of the Redis root.
* | Expire Rack sessions after 1 weekJacob Vosmaer2014-08-261-0/+1
|/
* Give the Rails cache its own Redis namespaceJacob Vosmaer2014-04-151-1/+1
| | | | | | | | Before this change, Rails cache data was stored in a global Redis namespace. As a consequence, clearing the Rails cache (`rake cache:clear`) would also delete all Sidekiq queue data and session storage. This change puts all Rails cache data in a `cache:gitlab` namespace, making `rake cache:clear` safe again.
* Enable secure option if https is used.Marin Jankovski2013-12-251-1/+1
|
* Respect the configured redis URL when initializing the session storevollnhals2013-10-301-0/+1
| | | | | | | | | It was not possible to start Gitlab with a redis server running on another host or port. Every other subsystem that uses redis respects the settings in config/resque.yml. This patch uses the configured url from the cache_store configuration. The cache_store configuration already loads the correct redis url from config/resque.yml. Closes #5406
* The cookie store is vulnerable to session replay attacks.Sytse Sijbrandij2013-10-111-9/+7
|
* Fixes grack authentification under relative_url_rootamouhzi2013-08-151-1/+2
| | | | | | | | | | | | | | | | | | | | | | Ref: https://github.com/gitlabhq/gitlabhq/commit/e6159b8725f99af78f446f8d33fa0e52b7780430 Ref: https://github.com/gitlabhq/gitlabhq/pull/3204 Ref: https://github.com/gitlabhq/gitlabhq/issues/1228 Add Rails' variable in application.rb to support relative url This variable is used by assets compilation and other modules. Note that user needs to change application.rb too Restrict session cookie to the relative path if set. Ref: https://github.com/gitlabhq/gitlabhq/commit/2c2f1e31856a4decdae469974f5bea8245316f7e Fix Update attachment_uploader.rb bug with relative URL See: https://github.com/gitlabhq/gitlabhq/commit/161afda3fa4fca58f396e9c3acbd72bc14490ace Fix Wall relative bug with attachement files (javascript)
* Secure and httponly options on cookie.Marin Jankovski2012-09-261-1/+3
|
* init commitgitlabhq2011-10-091-0/+8
View Lorry Controller Status