Tencent/WeKnora · error

fileName too long

Error message

fileName too long

What it means

Length validation in SafeFileName: the surviving path component exceeds 255 characters, beyond typical filesystem name limits. The name is rejected so a later OS-level write (e.g., in SaveBytes) cannot fail with a filesystem-dependent ENAMETOOLONG error; callers should shorten the filename.

Source

Thrown at internal/utils/security.go:142

	}
	return absPath, nil
}

// SafeFileName 校验并返回安全的“仅文件名”部分，防止路径遍历。
// 仅保留最后一个路径成分，禁止 ".."、空名或仅含点，用于 SaveBytes 等场景。
func SafeFileName(fileName string) (string, error) {
	if fileName == "" {
		return "", fmt.Errorf("fileName cannot be empty")
	}
	base := filepath.Base(filepath.Clean(fileName))
	if base == "" || base == "." || base == ".." {
		return "", fmt.Errorf("invalid fileName: path traversal or empty name")
	}
	if strings.Contains(base, "..") {
		return "", fmt.Errorf("invalid fileName: contains path traversal")
	}
	if len(base) > 255 {
		return "", fmt.Errorf("fileName too long")
	}
	return base, nil
}

// SafeObjectKey 校验对象存储的 key（如 COS/MinIO objectName），禁止包含 ".." 等路径遍历
func SafeObjectKey(objectKey string) error {
	if objectKey == "" {
		return fmt.Errorf("object key cannot be empty")
	}
	if strings.Contains(objectKey, "..") {
		return fmt.Errorf("object key contains path traversal")
	}
	return nil
}

// IsValidURL 验证 URL 是否安全
func IsValidURL(url string) bool {
	if url == "" {

View on GitHub (pinned to 988cbb0330)

Solutions

1. Truncate the file name to 255 bytes (preserving the extension)
2. Generate a shorter server-side name for very long client names

When it happens

Trigger: Thrown at internal/utils/security.go:142 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of Tencent/WeKnora@988cbb0330 (2026-09-02). Data as JSON: /api/errors/d09a4ca25dcd1be8. Report an issue: GitHub.