You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cyberduck/info.md
+69-30Lines changed: 69 additions & 30 deletions
Original file line number
Diff line number
Diff line change
@@ -40,10 +40,13 @@ Calculate the size recursively of all contained files.
40
40
Cyberduck [8.4](https://cyberduck.io/changelog/) or later required
41
41
```
42
42
43
-
A list of file versions can be viewed in the *Versions* tab of the Info window. The following actions are available for a selected previous version:
43
+
A list of file versions can be viewed in the *Versions* tab of the Info window. The following actions are available for
44
+
a selected previous version:
45
+
44
46
- Revert version
45
47
- Permanently delete version
46
-
- View previous version. On macOS, this opens a *QuickLook* window. On Windows, this downloads and opens the file in the default editor.
48
+
- View previous version. On macOS, this opens a *QuickLook* window. On Windows, this downloads and opens the file in the
49
+
default editor.
47
50
48
51
The list is empty when no previous version is available.
49
52
@@ -52,35 +55,44 @@ The list is empty when no previous version is available.
52
55
:width: 600px
53
56
```
54
57
55
-
The following protocols support to view previous versions of files. Some protocols also display previous versions of files in [browser](../cyberduck/browser.md) when enabling *View → Show Hidden*.
58
+
The following protocols support to view previous versions of files. Some protocols also display previous versions of
59
+
files in [browser](../cyberduck/browser.md) when enabling *View → Show Hidden*.
56
60
57
-
|**Protocol**|**Revert previous version**|**Open/Quick Look previous version**|**Delete version**|**Displayed in browser with *View → Show Hidden***|
Using [S3](../protocols/s3/index.md) or [Backblaze B2](../protocols/b2.md), versions will only be displayed if bucket versioning is enabled.
71
75
```
72
76
73
-
### Custom versioning
77
+
### Custom versioning
74
78
75
79
```{important}
76
80
Cyberduck [9.0](https://cyberduck.io/changelog/) or later required
77
81
```
78
82
79
-
To keep versions for protocols without native versioning support like [FTP](../protocols/ftp.md), [SFTP](../protocols/sftp/index.md), [WebDAV](../protocols/webdav/index.md) or [OpenStack Swift](../protocols/openstack/index.md), enable the [custom versioning option](edit.md#versioning) in *Preferences → Editor*.
83
+
To keep versions for protocols without native versioning support
84
+
like [FTP](../protocols/ftp.md), [SFTP](../protocols/sftp/index.md), [WebDAV](../protocols/webdav/index.md)
85
+
or [OpenStack Swift](../protocols/openstack/index.md), enable the [custom versioning option](edit.md#versioning) in
86
+
*Preferences → Editor*.
80
87
81
88
## UNIX Permissions
82
89
83
-
Change the permissions on a particular file or folder when connected to a [FTP](../protocols/ftp.md) or [SFTP](../protocols/sftp/index.md) server. You can also select multiple files in the browser to edit permissions. Click the checkboxes or enter the [octal notation](http://en.wikipedia.org/wiki/File_system_permissions#Symbolic_notation). The recursive options will update all files within a folder but will not change the executable bit for files if not already set when recursively updating a directory.
90
+
Change the permissions on a particular file or folder when connected to a [FTP](../protocols/ftp.md)
91
+
or [SFTP](../protocols/sftp/index.md) server. You can also select multiple files in the browser to edit permissions.
92
+
Click the checkboxes or enter
93
+
the [octal notation](http://en.wikipedia.org/wiki/File_system_permissions#Symbolic_notation). The recursive options will
94
+
update all files within a folder but will not change the executable bit for files if not already set when recursively
95
+
updating a directory.
84
96
85
97
```{image} _images/UNIX_Permissions.png
86
98
:alt: UNIX Permissions
@@ -89,7 +101,8 @@ Change the permissions on a particular file or folder when connected to a [FTP](
89
101
90
102
## Access Control List (ACL)
91
103
92
-
Edit access control list for fine grained user permissions when connected to [Amazon S3](../protocols/s3/index.md) or [Google Cloud Storage](../protocols/googlecloudstorage.md).
104
+
Edit access control list for fine grained user permissions when connected to [Amazon S3](../protocols/s3/index.md)
105
+
or [Google Cloud Storage](../protocols/googlecloudstorage.md).
Upon changing configuration parameters of a distribution configuration, the settings are not distributed immediately in the CDN. While the deployment is in progress (which can take up to 15 minutes), the status *In Progress* is displayed. The updates are fully propagated throughout the CloudFront system when the distribution's state switches from *In Progress* to *Deployed*.
122
+
Upon changing configuration parameters of a distribution configuration, the settings are not distributed immediately in
123
+
the CDN. While the deployment is in progress (which can take up to 15 minutes), the status *In Progress* is displayed.
124
+
The updates are fully propagated throughout the CloudFront system when the distribution's state switches from *In
125
+
Progress* to *Deployed*.
109
126
110
127
### CloudFront Access Logging
111
128
112
-
When this option is enabled, access logs are written to `<bucketname>/logs`. The changes to the logging configuration take effect within 12 hours. The logging option is supported for both download and streaming distributions. Choose the target bucket for access logs in the dropdown menu listing all buckets of your account. It is considered best practice to choose a different logging target for each distribution.
129
+
When this option is enabled, access logs are written to `<bucketname>/logs`. The changes to the logging configuration
130
+
take effect within 12 hours. The logging option is supported for both download and streaming distributions. Choose the
131
+
target bucket for access logs in the dropdown menu listing all buckets of your account. It is considered best practice
132
+
to choose a different logging target for each distribution.
113
133
114
134
### Origin
115
135
116
-
The source of the content where CloudFront fetches the content to be served in the edge location of the CDN. This is a [S3](../protocols/s3/index) bucket or your custom origin.
136
+
The source of the content where CloudFront fetches the content to be served in the edge location of the CDN. This is
137
+
a [S3](../protocols/s3/index) bucket or your custom origin.
117
138
118
139
### Where
119
-
The `cloudfront.net` domain assigned to your distribution. This is directing to the edge location in the CDN next to the user requesting an URL.
140
+
141
+
The `cloudfront.net` domain assigned to your distribution. This is directing to the edge location in the CDN next to the
142
+
user requesting an URL.
120
143
121
144
### CNAMEs
122
-
Enter a [CNAME](http://en.wikipedia.org/wiki/CNAME_record) (alias in the Domain Name System) for the hostname of the distribution given by CloudFront. To use multiple CNAMEs for a single distribution, the hostnames must be space delimited. The CNAME must be registered on the nameserver responsible for your domain and point to `cloudfront.net` domain assigned to your distribution.
145
+
146
+
Enter a [CNAME](http://en.wikipedia.org/wiki/CNAME_record) (alias in the Domain Name System) for the hostname of the
147
+
distribution given by CloudFront. To use multiple CNAMEs for a single distribution, the hostnames must be space
148
+
delimited. The CNAME must be registered on the nameserver responsible for your domain and point to `cloudfront.net`
149
+
domain assigned to your distribution.
123
150
124
151
Example configuration:
125
152
@@ -130,20 +157,30 @@ Example configuration:
130
157
cdn.cyberduck.ch. 1576 IN CNAME d15bfu8of7vup8.cloudfront.net.
131
158
132
159
### Index File
133
-
You can assign a default root object to your HTTP or HTTPS distribution. This default object will be served when Amazon CloudFront receives a request for the root of your distribution – i.e., your distribution’s domain name by itself.
134
160
135
-
When you define a default root object, a user request that calls the root of your distribution returns the default root object. For example, if you designate the file `index.html` as your default root object, a request for `http://d604721fxaaqy9.cloudfront.net/` returns `http://d604721fxaaqy9.cloudfront.net/index.html`.
161
+
You can assign a default root object to your HTTP or HTTPS distribution. This default object will be served when Amazon
162
+
CloudFront receives a request for the root of your distribution – i.e., your distribution’s domain name by itself.
163
+
164
+
When you define a default root object, a user request that calls the root of your distribution returns the default root
165
+
object. For example, if you designate the file `index.html` as your default root object, a request
166
+
for `http://d604721fxaaqy9.cloudfront.net/` returns `http://d604721fxaaqy9.cloudfront.net/index.html`.
136
167
137
168
### Object Invalidation
138
-
[Invalidation](http://aws.amazon.com/about-aws/whats-new/2010/08/31/cloudfront-adds-invalidation-feature/) is one way to remove a distribution object from an edge server cache before the expiration setting on the object's header. Invalidation clears the object from the edge server cache, and a subsequent request for the object will cause CloudFront to return to the origin to fetch the latest version of the object.
169
+
170
+
[Invalidation](http://aws.amazon.com/about-aws/whats-new/2010/08/31/cloudfront-adds-invalidation-feature/) is one way to
171
+
remove a distribution object from an edge server cache before the expiration setting on the object's header.
172
+
Invalidation clears the object from the edge server cache, and a subsequent request for the object will cause CloudFront
173
+
to return to the origin to fetch the latest version of the object.
139
174
140
175
```{note}
141
176
Use the Invalidate option *File → Info → Distribution (CDN)* to invalidate files from edge locations.
142
177
```
143
178
144
179
## Provider Panel
145
180
146
-
Settings specific for the cloud service in use. Available for [Amazon S3](../protocols/s3/index.md), [Backblaze B2](../protocols/b2.md), [Windows Azure Blob Storage](../protocols/azure.md), and [Google Cloud Storage](../protocols/googlecloudstorage.md).
181
+
Settings specific for the cloud service in use. Available
182
+
for [Amazon S3](../protocols/s3/index.md), [Backblaze B2](../protocols/b2.md), [Windows Azure Blob Storage](../protocols/azure.md),
183
+
and [Google Cloud Storage](../protocols/googlecloudstorage.md).
147
184
148
185
``````{tabs}
149
186
`````{group-tab} Amazon S3
@@ -205,9 +242,11 @@ Settings specific for the cloud service in use. Available for [Amazon S3](../pro
205
242
206
243
View and modify metadata attributes of files.
207
244
208
-
Any non-standard HTTP header values are (transparently) prefixed with the following values following the guidelines from the different providers:
245
+
Any non-standard HTTP header values are (transparently) prefixed with the following values following the guidelines from
246
+
the different providers:
209
247
210
-
- Values are prefixed with `x-amz-meta-` for [S3](../protocols/s3/index.md) and [Google Storage](../protocols/googlecloudstorage.md).
248
+
- Values are prefixed with `x-amz-meta-` for [S3](../protocols/s3/index.md)
249
+
and [Google Storage](../protocols/googlecloudstorage.md).
211
250
- Values are prefixed with `X-Object-Meta-` for [CloudFiles](../protocols/openstack/cloudfiles.md).
0 commit comments