Use NamespaceValidator::WILDCARD_ROUTES in ETag caching middleware

NamespaceValidator::WILDCARD_ROUTES is less restrictive than ProjectPathValidator::RESERVED and we really have to avoid only routes that contain wildcard names.

Use NamespaceValidator::WILDCARD_ROUTES in ETag caching middleware
63a6453c · Adam Niedzielski · d4349ba6 · 63a6453c
Commit 63a6453c authored Apr 05, 2017 by Adam Niedzielski
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

middleware.rb lib/gitlab/etag_caching/middleware.rb +1 -1

No files found.
--- a/lib/gitlab/etag_caching/middleware.rb
+++ b/lib/gitlab/etag_caching/middleware.rb
 module Gitlab
  module EtagCaching
    class Middleware
-      RESERVED_WORDS = ProjectPathValidator::RESERVED.map { |word| "/#{word}/" }.join('|')
+      RESERVED_WORDS = NamespaceValidator::WILDCARD_ROUTES.map { |word| "/#{word}/" }.join('|')
      ROUTE_REGEXP = Regexp.union(
        %r(^(?!.*(#{RESERVED_WORDS})).*/noteable/issue/\d+/notes\z)
      )