Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-05-02Display and revoke active sessionsAlexis Reigel ( 🌴 may 2nd - may 9th 🌴 )
2017-08-31`current_application_settings` belongs on `Gitlab::CurrentSettings`Sean McGivern
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.
2017-07-11Support multiple Redis instances based on queue typePaul Charlton
2017-06-01Update session cookie key name to be unique to instance in developmentEric Eastwood
Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/31644
2016-08-04Deduplicated resque.yml loading from several placesGabriel Mazetto
We will trust redis configuration params loading to Gitlab::RedisConfig.
2016-05-30Enable Style/RedundantParentheses rubocop copGrzegorz Bizon
See #17478
2016-05-02Fix "remember me" sign in optionJacob Vosmaer
2016-04-13Redis configuration consistencyValery Sizov
2016-04-04Add Gitlab::Redis connection poolJacob Vosmaer
2016-03-09Parse config/resque.yml in one place onlyJacob Vosmaer
2015-12-02Merge branch 'master' into reference-pipeline-and-cachingDouwe Maan
2015-11-25Rails update to 4.2.4Valery Sizov
2015-11-24Also fallback to a default value if none is set.Marin Jankovski
2015-11-24Maybe rescue session_expire_delay by setting a default value.Marin Jankovski
2015-11-16Disabling cache for test environmentValery Sizov
2015-10-22Disabling caching in test environment because it was causing issues with ↵Douwe Maan
Markdown
2015-09-11Merge branch 'master' into ci-and-ce-sitting-in-a-tree-k-i-s-s-i-n-gDmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2015-09-09Fix reading session_expire_delay when application settings are not yet ↵Kamil Trzcinski
created and migrations are not yet done
2015-08-26Groundwork for merging CI into CEDouwe Maan
2015-06-13Ensure `session_expire_delay` field exists before accessing itRobert Speicher
Closes #1798
2015-06-11session_expire_seconds => session_expire_delaythemaze75
delay is in seconds more legible code in session_store Added `GitLab restart required` help block to session_expire_delay
2015-06-05Add session expiration delay configuration through UI applicationEric Maziade
settings
2014-08-28Merge branch 'redis_settings'Dmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> Conflicts: CHANGELOG
2014-08-26Store sessions in a Redis namespaceJacob Vosmaer
This makes less of a mess of the Redis root.
2014-08-26Expire Rack sessions after 1 weekJacob Vosmaer
2014-04-15Give the Rails cache its own Redis namespaceJacob Vosmaer
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.
2013-12-25Enable secure option if https is used.Marin Jankovski
2013-10-30Respect the configured redis URL when initializing the session storevollnhals
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
2013-10-11The cookie store is vulnerable to session replay attacks.Sytse Sijbrandij
2013-08-15Fixes grack authentification under relative_url_rootamouhzi
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)
2012-09-26Secure and httponly options on cookie.Marin Jankovski
2011-10-09init commitgitlabhq