Коммит 4fa8c19a создал по автору Achilleas Pipinellis (OOO | back on july 25th)'s avatar Achilleas Pipinellis (OOO | back on july 25th) Зафиксировано автором Clayton Cornell
Просмотр файлов

Remove trailing spaces from the docs 

For https://gitlab.com/gitlab-org/technical-writing/-/issues/619
владелец cb31fbf0
Скрыть пробелы
Построчно Рядом
doc/administration/geo/replication/troubleshooting.md
Просмотр файла @ 4fa8c19a
......@@ -817,16 +817,16 @@ end
### Message: curl 18 transfer closed with outstanding read data remaining & fetch-pack: unexpected disconnect while reading sideband packet
Unstable networking conditions can cause Gitaly to fail when trying to fetch large repository
Unstable networking conditions can cause Gitaly to fail when trying to fetch large repository
data from the primary site. This is more likely to happen if a repository has to be
replicated from scratch between sites.
Geo retries several times, but if the transmission is consistently interrupted
by network hiccups, an alternative method such as `rsync` can be used to circumvent `git` and
by network hiccups, an alternative method such as `rsync` can be used to circumvent `git` and
create the initial copy of any repository that fails to be replicated by Geo.
We recommend transferring each failing repository individually and checking for consistency
after each transfer. Follow the [single target `rsync` instructions](../../operations/moving_repositories.md#single-rsync-to-another-server)
after each transfer. Follow the [single target `rsync` instructions](../../operations/moving_repositories.md#single-rsync-to-another-server)
to transfer each affected repository from the primary to the secondary site.
## Fixing errors during a failover or when promoting a secondary to a primary node
......
doc/administration/gitaly/configure_gitaly.md
Просмотр файла @ 4fa8c19a
......@@ -904,7 +904,7 @@ gitaly['cgroups_repositories_cpu_shares'] => 512
which represents 100% of CPU. This value cannot exceed that of the top
level`cgroups_cpu_shares`.
#### Configure cgroups (legacy method)
#### Configure cgroups (legacy method)
To configure cgroups in Gitaly for GitLab versions using the legacy method, add `gitaly['cgroups']` to `/etc/gitlab/gitlab.rb`. For
example:
......
doc/administration/object_storage.md
Просмотр файла @ 4fa8c19a
......@@ -542,7 +542,7 @@ supported by consolidated configuration form, refer to the following guides:
| [Pages content](pages/index.md#using-object-storage) | **{check-circle}** Yes |
WARNING:
The use of [encrypted S3 buckets](#encrypted-s3-buckets) with non-consolidated configuration is not supported.
The use of [encrypted S3 buckets](#encrypted-s3-buckets) with non-consolidated configuration is not supported.
You may start getting [ETag mismatch errors](#etag-mismatch) if you use it.
### Other alternatives to file system storage
......
doc/api/metadata.md
Просмотр файла @ 4fa8c19a
......@@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/357032) in GitLab 15.2.
Retrieve metadata information for this GitLab instance.
Retrieve metadata information for this GitLab instance.
```plaintext
GET /metadata
......
doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md
Просмотр файла @ 4fa8c19a
......@@ -262,7 +262,7 @@ details about how to configure SAST, see the SAST [documentation](../../../user/
### Configure DAST
To use [DAST](../../../user/application_security/dast/index.md) on non-default branches, [set up review apps](#set-up-review-apps)
and then follow the steps outlined in the DAST [documentation](../../../user/application_security/dast/index.md).
and then follow the steps outlined in the DAST [documentation](../../../user/application_security/dast/index.md).
## Further reading
......
doc/ci/testing/code_quality.md
Просмотр файла @ 4fa8c19a
......@@ -333,7 +333,7 @@ code_quality:
CODECLIMATE_PREFIX: "my-private-registry.local:12345/"
```
The images in the private container image registry must be available without authentication.
The images in the private container image registry must be available without authentication.
Follow [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/355814) for more information.
This example is specific to GitLab Code Quality. For more general
......
doc/development/cicd/pipeline_wizard.md
Просмотр файла @ 4fa8c19a
......@@ -230,7 +230,7 @@ Use as `widget: list`. This inserts a `list` in the YAML file.
#### Checklist
Use as `widget: checklist`. This inserts a list of checkboxes that need to
Use as `widget: checklist`. This inserts a list of checkboxes that need to
be checked before proceeding to the next step.
| Name | Required | Type | Description |
......
doc/development/code_review.md
Просмотр файла @ 4fa8c19a
......@@ -306,7 +306,7 @@ A maintainer should ask the author to make a merge request smaller if it is:
- Has a high complexity resulting in additional risk.
The maintainer, any of the
reviewers, or a merge request coach can step up to help the author to divide work
reviewers, or a merge request coach can step up to help the author to divide work
into smaller iterations, and guide the author on how to split the merge request.
The author may choose to request that the current maintainers and reviewers review the split MRs
or request a new group of maintainers and reviewers.
......
doc/development/gitlab_flavored_markdown/specification_guide/index.md
Просмотр файла @ 4fa8c19a
......@@ -401,7 +401,7 @@ The documentation on the implementation is split into three sections:
1. [Scripts](#scripts).
1. [Specification files](#specification-files).
1. [Example snapshot files](#example-snapshot-files):
1. [Example snapshot files](#example-snapshot-files):
These YAML files are used as input data
or fixtures to drive the various tests, and are located under
`glfm_specification/example_snapshots`. All example snapshot files are automatically
......
doc/development/pipelines.md
Просмотр файла @ 4fa8c19a
......@@ -299,7 +299,7 @@ test causing the failure:
1. Run `SIMPLECOV=1 bundle exec rspec <spec>`.
1. Run `scripts/undercoverage`.
If these commands return `undercover: ✅ No coverage is missing in latest changes` then you can apply `~"pipeline:skip-undercoverage"` to bypass pipeline failures.
If these commands return `undercover: ✅ No coverage is missing in latest changes` then you can apply `~"pipeline:skip-undercoverage"` to bypass pipeline failures.
## Ruby versions testing
......
doc/development/snowplow/implementation.md
Просмотр файла @ 4fa8c19a
......@@ -464,7 +464,7 @@ Page titles are hardcoded as `GitLab` for the same reason.
#### Snowplow Inspector Chrome Extension
Snowplow Inspector Chrome Extension is a browser extension for testing frontend events. This works in production, staging, and local development environments.
Snowplow Inspector Chrome Extension is a browser extension for testing frontend events. This works in production, staging, and local development environments.
<i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
For a video tutorial, see the [Snowplow plugin walk through](https://www.youtube.com/watch?v=g4rqnIZ1Mb4).
......
doc/integration/advanced_search/elasticsearch.md
Просмотр файла @ 4fa8c19a
......@@ -296,7 +296,7 @@ To disable the Elasticsearch integration:
bundle exec rake gitlab:elastic:delete_index RAILS_ENV=production
```
## Unpause Indexing
## Unpause Indexing
1. On the top bar, select **Menu > Admin**.
1. On the left sidebar, select **Settings > Advanced Search**.
......
doc/integration/jira/index.md
Просмотр файла @ 4fa8c19a
......@@ -119,6 +119,6 @@ and complete the CAPTCHA.
### Jira integration does not work for imported project
There is a [known bug](https://gitlab.com/gitlab-org/gitlab/-/issues/341571)
where the Jira integration sometimes does not work for a project that has been imported.
There is a [known bug](https://gitlab.com/gitlab-org/gitlab/-/issues/341571)
where the Jira integration sometimes does not work for a project that has been imported.
As a workaround, disable the integration and then re-enable it.
doc/user/application_security/dast/checks/209.1.md
Просмотр файла @ 4fa8c19a
......@@ -9,17 +9,17 @@ info: To determine the technical writer assigned to the Stage/Group associated w
## Description
The application was found to return error data such as stack traces. Depending on the data contained within the error message,
this information could be used by an attacker to conduct further attacks. While stack traces are helpful during development
and debugging, they should not be presented to users when an error occurs.
this information could be used by an attacker to conduct further attacks. While stack traces are helpful during development
and debugging, they should not be presented to users when an error occurs.
## Remediation
Applications should handle exception conditions internally and map known failure types to error codes that can be displayed
to a user. These error codes should be customized to the application and returned along with the relevant HTTP error code.
When an error occurs, the application identifies the error type or class, and displays a numerical value to the
user. Requests should also be tracked so when a user is presented with an error code, it has a corresponding request ID.
Support teams can then correlate the HTTP error, the customized error code, and the request ID in the log files to
When an error occurs, the application identifies the error type or class, and displays a numerical value to the
user. Requests should also be tracked so when a user is presented with an error code, it has a corresponding request ID.
Support teams can then correlate the HTTP error, the customized error code, and the request ID in the log files to
determine the root cause of the error without leaking details to the end user.
Example of returning customized errors:
......
doc/user/application_security/dast/checks/209.2.md
Просмотр файла @ 4fa8c19a
......@@ -9,17 +9,17 @@ info: To determine the technical writer assigned to the Stage/Group associated w
## Description
The application was found to return database error messages. Determining the type of database may assist attackers in exploiting
SQL Injection attacks against the system. While debug messages are helpful during development and debugging, they should not be
presented to users when an error occurs.
SQL Injection attacks against the system. While debug messages are helpful during development and debugging, they should not be
presented to users when an error occurs.
## Remediation
Applications should handle database error conditions internally and map known failure types to error codes that can be displayed
to a user. These error codes should be customized to the application and returned along with the relevant HTTP error code.
When an error occurs, the application identifies the error type or class, and displays a numerical value to the
user. Requests should also be tracked so when a user is presented with an error code, it has a corresponding request ID.
Support teams can then correlate the HTTP error, the customized error code, and the request ID in the log files to
When an error occurs, the application identifies the error type or class, and displays a numerical value to the
user. Requests should also be tracked so when a user is presented with an error code, it has a corresponding request ID.
Support teams can then correlate the HTTP error, the customized error code, and the request ID in the log files to
determine the root cause of the error without leaking details to the end user.
Example of returning customized errors:
......
doc/user/application_security/dast/checks/319.1.md
Просмотр файла @ 4fa8c19a
......@@ -9,19 +9,19 @@ info: To determine the technical writer assigned to the Stage/Group associated w
## Description
The target application was found to request resources over insecure transport protocols (HTTP). This is usually due to HTML
elements which load resources using the `http://` scheme instead of `https://`. It should be noted that most modern browsers
block these requests automatically so there is limited risk.
elements which load resources using the `http://` scheme instead of `https://`. It should be noted that most modern browsers
block these requests automatically so there is limited risk.
Some parts of the application may not behave correctly since these files are not being properly loaded.
## Remediation
Ensure all HTML elements which load resources from a URL (JavaScript, stylesheets, images, video and other media) are set to
Ensure all HTML elements which load resources from a URL (JavaScript, stylesheets, images, video and other media) are set to
use the `https://` scheme instead of `http://`. Alternatively, developers may use the `//` scheme, which will only load resources
over the same protocol that the originating page was loaded.
over the same protocol that the originating page was loaded.
A browser visiting the website `https://example.com` with the HTML loading a file using
`<script src="//example.com/cdn/bundle.js"></script>`, would ensure the `example.com/cdn/bundle.js` file was loaded over
A browser visiting the website `https://example.com` with the HTML loading a file using
`<script src="//example.com/cdn/bundle.js"></script>`, would ensure the `example.com/cdn/bundle.js` file was loaded over
HTTPS.
## Details
......
doc/user/application_security/dast/checks/601.1.md
Просмотр файла @ 4fa8c19a
......@@ -8,17 +8,17 @@ info: To determine the technical writer assigned to the Stage/Group associated w
## Description
This site was found to allow open redirects from user supplied input. Open redirects are commonly
abused in phishing attacks where the original domain or URL looks like a legitimate link, but then
redirects a user to a malicious site. An example would be
`https://example.com/redirect?url=https://%62%61%64%2e%63%6f%6d%2f%66%61%6b%65%6c%6f%67%69%6e` which,
This site was found to allow open redirects from user supplied input. Open redirects are commonly
abused in phishing attacks where the original domain or URL looks like a legitimate link, but then
redirects a user to a malicious site. An example would be
`https://example.com/redirect?url=https://%62%61%64%2e%63%6f%6d%2f%66%61%6b%65%6c%6f%67%69%6e` which,
when decoded turns into `bad.com/fakelogin`.
## Remediation
Never redirect a client based on user input found in a `GET` request. It is recommended that the list
of target links to redirect a user to are contained server side, and retrieved using a numerical value
as an index to return the link to be redirected to. For example, `/redirect?id=1` would cause the
Never redirect a client based on user input found in a `GET` request. It is recommended that the list
of target links to redirect a user to are contained server side, and retrieved using a numerical value
as an index to return the link to be redirected to. For example, `/redirect?id=1` would cause the
application to look up the `1` index and return a URL such as `https://example.com`. This URL would
then be used to redirect the user, using the 301 response code and `Location` header.
......
doc/user/clusters/agent/troubleshooting.md
Просмотр файла @ 4fa8c19a
......@@ -200,11 +200,11 @@ are stored in the repository where the agent is configured.
```
The GitLab agent for Kubernetes has been able to run [vulnerability scans](vulnerabilities.md) since GitLab 15.0. However, the agent
cannot detect the service account name. Refer to [issue 361972](https://gitlab.com/gitlab-org/gitlab/-/issues/361972) for more
cannot detect the service account name. Refer to [issue 361972](https://gitlab.com/gitlab-org/gitlab/-/issues/361972) for more
information. As a workaround you can pass the `--set serviceAccount.name=gitlab-agent` parameter
to the Helm command when [installing the agent](install/#install-the-agent-in-the-cluster), or manually create a service account.
```shell
```shell
kubectl create serviceaccount gitlab-agent -n gitlab-agent
```
......
doc/user/group/import/index.md
Просмотр файла @ 4fa8c19a
......@@ -86,7 +86,7 @@ migrated:
- Badges ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/292431) in 13.11)
- Board Lists
- Boards
- Boards
- Epics ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/250281) in 13.7)
- Finisher
- Group Labels ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/292429) in 13.9)
......
doc/user/infrastructure/iac/troubleshooting.md
Просмотр файла @ 4fa8c19a
......@@ -113,7 +113,7 @@ job that returned the error:
1. Configure the [CI/CD environment scope](../../../ci/variables/#add-a-cicd-variable-to-a-project) for the job.
1. Set the job's [environment](../../../ci/yaml/#environment), matching the environment scope from the previous step.
### Error refreshing state: HTTP remote state endpoint requires auth
### Error refreshing state: HTTP remote state endpoint requires auth
To resolve this, ensure that:
......
Поддерживает Markdown
0% или .
You are about to add 0 people to the discussion. Proceed with caution.
Сначала завершите редактирование этого сообщения!
Пожалуйста, зарегистрируйтесь или чтобы прокомментировать