-
- Downloads
Switch use of Rack::Request to ActionDispatch::Request
As mentioned in https://gitlab.com/gitlab-org/gitlab-ee/issues/9035#note_129093444, Rails 5 switched ActionDispatch::Request so that it no longer inherits Rack::Request directly. A middleware that uses Rack::Request to read the environment may see stale request parameters if another middleware modifies the environment via ActionDispatch::Request. To be safe, we should be using ActionDispatch::Request everywhere.
Showing
- lib/api/helpers.rb 1 addition, 1 deletionlib/api/helpers.rb
- lib/gitlab/etag_caching/middleware.rb 1 addition, 1 deletionlib/gitlab/etag_caching/middleware.rb
- lib/gitlab/middleware/basic_health_check.rb 1 addition, 1 deletionlib/gitlab/middleware/basic_health_check.rb
- lib/gitlab/middleware/read_only/controller.rb 1 addition, 1 deletionlib/gitlab/middleware/read_only/controller.rb
- lib/gitlab/request_context.rb 1 addition, 1 deletionlib/gitlab/request_context.rb
- spec/lib/gitlab/auth/user_auth_finders_spec.rb 1 addition, 1 deletionspec/lib/gitlab/auth/user_auth_finders_spec.rb
- spec/lib/gitlab/request_context_spec.rb 1 addition, 1 deletionspec/lib/gitlab/request_context_spec.rb
- spec/lib/omni_auth/strategies/jwt_spec.rb 2 additions, 0 deletionsspec/lib/omni_auth/strategies/jwt_spec.rb
- spec/requests/git_http_spec.rb 2 additions, 2 deletionsspec/requests/git_http_spec.rb
Please register or sign in to comment