Skip to content

Commit c8e54bd

Browse files
Moves 10xxx to individual pages (#22488)
1 parent 5bb5f56 commit c8e54bd

File tree

19 files changed

+401
-0
lines changed

19 files changed

+401
-0
lines changed
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
pcx_content_type: troubleshooting
3+
title: Error 10028
4+
source: null
5+
---
6+
7+
## Error 10028: The add list items operation contains duplicate items
8+
9+
This error indicates that the operation to add items to a list contains duplicate entries within the same request.
10+
11+
### Common causes
12+
13+
This error occurs when there are duplicate list items in a single operation to add items to a List (either an IP list or a Bulk Redirect List). This error can happen when you:
14+
15+
- Add a repeated IP address to an IP list
16+
- Add a repeated source URL to a Bulk Redirect List
17+
18+
### Resolution
19+
20+
You need to remove the duplicate item and try again.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
pcx_content_type: troubleshooting
3+
title: Error 10043
4+
source: null
5+
---
6+
7+
## Error 10043: Source URL in redirect is too long
8+
9+
This error indicates that the source URL in a redirect exceeds the maximum allowed length.
10+
11+
### Common causes
12+
13+
This error occurs when the source URL value of a URL redirect is too long. The maximum length of a source URL is 32,768 characters. Possible causes of this error are:
14+
15+
- Dynamic URLs that contain excessive query parameters or tracking codes.
16+
- Unnecessary path segments or redundant subdirectories in the URL.
17+
18+
### Resolution
19+
20+
You need to use a shorter URL as the source URL.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
pcx_content_type: troubleshooting
3+
title: Error 10044
4+
source: null
5+
---
6+
7+
## Error 10044: Target URL in redirect is too long
8+
9+
This error indicates that the target URL in a redirect exceeds the maximum allowed length.
10+
11+
### Common causes
12+
13+
This error occurs when the target URL value of a URL redirect is too long. The maximum length of a target URL is 32,768 characters. Possible causes of this error are:
14+
15+
- Dynamic URLs that contain excessive query parameters or tracking codes.
16+
- Unnecessary path segments or redundant subdirectories in the URL.
17+
18+
### Resolution
19+
20+
You need to use a shorter URL as the target URL.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
pcx_content_type: troubleshooting
3+
title: Error 10045
4+
source: null
5+
---
6+
7+
## Error 10045: Invalid redirect source URL
8+
9+
This error indicates that the source URL for a redirect is not valid.
10+
11+
### Common causes
12+
13+
This error occurs when the source URL provided for a URL redirect is not valid, preventing the redirect from functioning properly due to missing components, such as the scheme (for instance, `http` or `https`) or improper formatting.
14+
15+
### Resolution
16+
17+
You need to specify a valid URL as the source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
pcx_content_type: troubleshooting
3+
title: Error 10046
4+
source: null
5+
---
6+
7+
## Error 10046: Invalid redirect target URL
8+
9+
This error indicates that the target URL provided for a URL redirect is not valid.
10+
11+
### Common causes
12+
13+
This error occurs when the target URL provided for a URL redirect is not valid, preventing the redirect from functioning properly due to missing components, such as the scheme (for instance, `http` or `https`) or improper formatting.
14+
15+
### Resolution
16+
17+
You need to specify a valid URL as the target URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect target URLs.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
pcx_content_type: troubleshooting
3+
title: Error 10047
4+
source: null
5+
---
6+
7+
## Error 10047: Invalid redirect status code
8+
9+
This error indicates that an unsupported or incorrectly formatted status code was specified for the URL redirect.
10+
11+
### Common causes
12+
13+
This error occurs when you specify a URL redirect status code that is not supported, typically due to entering an invalid number or using an unsupported or deprecated status code.
14+
15+
### Resolution
16+
17+
Use one of the supported status codes in the URL redirect: `301`, `302`, `307`, or `308`.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
pcx_content_type: troubleshooting
3+
title: Error 10048
4+
source: null
5+
---
6+
7+
## Error 10048: Preserve path suffix requires subpath matching enabled
8+
9+
This error indicates a configuration mismatch where the **Preserve path suffix** option is used without enabling **Subpath matching** in a URL redirect.
10+
11+
### Common causes
12+
13+
This error occurs when you enable the **Preserve path suffix** option in a redirect without enabling the **Subpath matching** option. The **Preserve path suffix** option of a URL redirect is only applicable when the **Subpath matching** option is also enabled.
14+
15+
### Resolution
16+
17+
Enable **Subpath matching** for the URL redirect with **Preserve path suffix** enabled.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
pcx_content_type: troubleshooting
3+
title: Error 10049
4+
source: null
5+
---
6+
7+
## Error 10049: Invalid scheme in redirect source URL
8+
9+
This error indicates that the source URL's scheme is invalid.
10+
11+
### Common causes
12+
13+
This error occurs when the source URL of a URL redirect has an invalid scheme, which may be due to a misspelled or unsupported scheme or because the scheme is missing or improperly formatted.
14+
15+
### Resolution
16+
17+
Review the source URL and ensure that it uses one of the supported schemes: `http`, `https`, or empty (no scheme information, which means that it applies to both schemes). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
pcx_content_type: troubleshooting
3+
title: Error 10050
4+
source: null
5+
---
6+
7+
## Error 10050: Invalid redirect source URL with user info
8+
9+
This error indicates that the source URL includes unsupported user information.
10+
11+
### Common causes
12+
13+
This error occurs when the source URL of a URL redirect includes a user info component (for example, `https://user:[email protected]`), which is not supported.
14+
15+
### Resolution
16+
17+
You need to remove the user information component from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs.
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
pcx_content_type: troubleshooting
3+
title: Error 10051
4+
source: null
5+
---
6+
7+
## Error 10051: Missing authority in redirect source URL
8+
9+
This error indicates that the source URL is missing a required authority component.
10+
11+
### Common causes
12+
13+
This error occurs when the source URL of a URL redirect does not include an authority component (for example, `http:///path`, without a hostname), which is mandatory.
14+
15+
### Resolution
16+
17+
Add an authority component to the redirect source URL (for example, include a hostname). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect source URLs.

0 commit comments

Comments
 (0)