Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
15a49784
Commit
15a49784
authored
Oct 29, 2020
by
Thong Kuah
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify that 13.1.X is OK for csrf changes
The global_csrf_token FF was removed in 13.2.0
parent
24490f47
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/update/README.md
doc/update/README.md
+2
-2
No files found.
doc/update/README.md
View file @
15a49784
...
...
@@ -263,9 +263,9 @@ with the older Rails version - which could cause non-GET requests to
fail for
[
multi-node GitLab installations
](
https://docs.gitlab.com/omnibus/update/#multi-node--ha-deployment
)
.
So, if you are using multiple Rails servers and specifically upgrading from 13.0,
all servers must first be upgraded to 13.1.
0 before upgrading to later versions
:
all servers must first be upgraded to 13.1.
X before upgrading to 13.2.0 or later
:
1.
Ensure all GitLab web nodes are on GitLab 13.1.
0
.
1.
Ensure all GitLab web nodes are on GitLab 13.1.
X
.
1.
Optionally, enable the
`global_csrf_token`
feature flag to enable new
method of CSRF token generation:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment