Dell DX6004S DX Object Storage SCSP Proxy Overview - Page 7

Examples of using /_proxy Syntax

Page 7 highlights

Syntax /_proxy/remote/uuid-or-name Description If the object exists in the local cluster the information is returned. Otherwise, the request is sent to each remote cluster in random order. If no cluster is able to locate the data, the error response from the local server is returned. remote is valid only for remote INFO requests and results in an error if used with any other method. remote causes a request for an object to be sent, referenced by UUID or by name, to a remote cluster. The information is returned from the first cluster that has the object. If the object cannot be found in any of the remote clusters, the error response that was received from the first remote cluster tried is returned. Note Support for remote proxy requests without the _proxy/ prefix is deprecated in this release and will be removed altogether in a future release. 1.2.1. Examples of using /_proxy Syntax As the following examples show, you must separate the URI from the domain specification using the slash character (/). In all cases, except where noted, the domain name must be passed as the Host in the request. Examples follow: • AggregateInfo of domain on either a local or remote cluster Local cluster: GET /_proxy/uuid?indirect=HEAD Remote cluster: GET /_proxy/cluster-name/uuid?indirect=HEAD For more information about AggregateInfo, see Section 1.2.3, "Remote Aggregate Info". • HEAD of a domain on either a remote or any cluster Remote cluster: HEAD /_proxy/remote?domain=domain-name Any cluster: HEAD /_proxy/any?domain=domain-name Note The domain= query argument is required whenever you perform an operation (in this case, HEAD) on a domain. • POST of an unnamed object to the default cluster domain POST /_proxy/cluster-name/ Copyright © 2010 Caringo, Inc. All rights reserved 4 Version 1.2 December 2010

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19

Copyright © 2010 Caringo, Inc.
All rights reserved
4
Version 1.2
December 2010
Syntax
Description
If the object exists in the local cluster the information
is returned. Otherwise, the request is sent to each
remote cluster in random order. If no cluster is able
to locate the data, the error response from the local
server is returned.
/_proxy/remote/
uuid-or-name
remote
is valid only for remote INFO requests and
results in an error if used with any other method.
remote
causes a request for an object to be sent,
referenced by UUID or by name, to a remote cluster.
The information is returned from the first cluster
that has the object. If the object cannot be found in
any of the remote clusters, the error response that
was received from the first remote cluster tried is
returned.
Note
Support for remote proxy requests without the
_proxy/
prefix is deprecated in this
release and will be removed altogether in a future release.
1.2.1. Examples of using /_proxy Syntax
As the following examples show, you must separate the URI from the domain specification using the
slash character (
/
). In all cases, except where noted, the domain name must be passed as the Host
in the request.
Examples follow:
AggregateInfo of domain on either a local or remote cluster
Local cluster
:
GET /_proxy/
uuid
?indirect=HEAD
Remote cluster
:
GET /_proxy/
cluster-name
/
uuid
?indirect=HEAD
For more information about AggregateInfo, see
Section 1.2.3, “Remote Aggregate Info”
.
HEAD of a domain on either a
remote
or
any
cluster
Remote cluster
:
HEAD /_proxy/remote?domain=
domain-name
Any cluster
:
HEAD /_proxy/any?domain=
domain-name
Note
The
domain=
query argument is required whenever you perform an operation (in this
case, HEAD) on a domain.
POST of an unnamed object to the default cluster domain
POST /_proxy/
cluster-name
/