files/{fileid}/properties (POST)
Overview
Create an attachment property
- REST Method: POST
- Method Access: public
Uri Parameters
Name | Type | Description |
fileid | int | identifies a file by ID |
Query Parameters
Name | Type | Description |
authenticate | bool? | Force authentication for request (default: false) |
abort | {never, modified, exists}? | Specifies condition under which to prevent the creation; default is exists. |
redirects | int? | If zero, do not follow page redirects. |
description | string? | Description of property |
Return Codes
Name | Value | Description |
OK | 200 | The request completed successfully |
Bad Request | 400 | Invalid input parameter or request body |
Forbidden | 403 | UPDATE access is required |
Not Found | 404 | Requested file could not be found |
Message Format
Input is an HTTP request containing a Slug header with the name of the property, a Content-Type header, a Content-Length, and the pro
POST /@api/deki/files/x/properties?description=description of foo Host: wikihost Slug: foo Content-Type: image/jpg Content-Length: 12345 ... data here ...
Response is the standard property XML
<property name="{text}" href="{uri}" etag="{text}"> <contents type="{text}" href="{uri}">{text}</contents> <date.modified>{date}</date.modified> <user.modified id="{int}" href="{uri}"> <nick>{text}</nick> <username>{text}</username> </user.modified> <change-description>{text}</change-description> </property>
Implementation Notes
- The response XML will contain the contents text only for text based mimetypes with values less than 2048 chars in length. Otherwise the contents is available at the URI pointed to by property/contents/@href.
- UPDATE rights to the parent page of a file is necessary to create or change a file property value. READ access is required to get the properties and its metadata.
C# Code Sample: Add File Property
The following code authenticates and creates a new file property named 'foo' with a text value. A description of the change is set as well.
Sample Code
Plug p = Plug.New("http://devwiki/@api/deki"); p.At("users", "authenticate") .WithCredentials("sysop", "password").Get(); p.At("files", "42", "properties") .WithHeader("Slug", "foo") .With("description", "initial value") .Post(DreamMessage.Ok(MimeType.TEXT_UTF8, "My Value"));
Sample Response from executing Code
<property name="foo" href="http://devwiki/@api/deki/files/42/properties/foo/info" etag="4463.r1_ts2009-03-20T22:48:15Z"> <contents type="text/plain; charset=utf-8" href="http://devwiki/@api/deki/files/42/properties/foo">My Value</contents> <date.modified>2009-03-20T22:48:15Z</date.modified> <user.modified id="1" href="http://devwiki/@api/deki/users/1"> <nick>Sysop</nick> <username>Sysop</username> </user.modified> <change-description>initial value</change-description> </property>
Curl Code Sample: Add File Property
The following command adds a file property to a file (file ID = 1) with property name "foo" and pairs it with the data from file "bar".
Sample Code
curl -u username:password -H "Content-Type: text/plain" -H "Slug: foo" -d @bar -i http://mindtouch.address/@api/deki/files/1/properties
Implementation notes
curl flags
- -u
- Basic HTTP authentication. Sends a username and password to server so it can verify whether a user is of privilege to perform specific operation.
- -d @file
- Specifies a POST request and the data file to send.
- -H
- Replaces or appends an HTTP header. The "Slug" header designates the property name. The "Content-Type" header specifies the MIME type of the value attached to the property.
- -i
- Includes the HTTP response header in the output. Useful for debugging.
MIMEs
- Properties can contain any type of file, therefore it is important to specify the correct MIME when creating a property. For instance, a text property will require a text/plain header, xml will require application/xml header, a jpeg image will require image/jpg header, and so on.
Example
We want to create a simple text property for an image with file ID = 9. The property name will be "iscopyright" and the value will be "no", as outlined in "imageprop.txt".
imageprop.txt
Content-Type: text/plain
no
Sample Code
curl -u username:password -H "Content-Type: text/plain" -H "Slug: iscopyright" -d @imageprop.txt -i http://192.168.168.110/@api/deki/files/9/properties
HTTP Response Headers
HTTP/1.1 200 OK Date: Tue, 12 Jan 2010 00:41:49 GMT Server: Dream-HTTPAPI/1.7.2.17433 X-Deki-Site: id="default" Content-Type: application/xml; charset=utf-8 Content-Length: 679 Via: 1.1 dekiwiki
HTTP Response Body
Content-Type: application/xml
<?xml version="1.0"?> <property name="iscopyright" href="http://192.168.168.110/@api/deki/files/9/properties/iscopyright/info" etag="34.r1_ts2010-01-12T00:41:49Z"> <contents type="text/plain" size="2" href="http://192.168.168.110/@api/deki/files/9/properties/iscopyright">no</contents> <date.modified>2010-01-12T00:41:49Z</date.modified> <user.modified id="1" href="http://192.168.168.110/@api/deki/users/1"> <nick>Admin</nick> <username>Admin</username> <email>melder@mindtouch.com</email> <hash.email>637b79dca5c8ebdc4347bccca42d3487</hash.email> <uri.gravatar>http://www.gravatar.com/avatar/637b79dca5c8ebdc4347bccca42d3487</uri.gravatar> </user.modified> <change-description/> </property>
Notes
- In order for properties to be displayed in "Page Properties" pages, the property name must be prefixed with "urn:custom.mindtouch.com#", otherwise it will remain hidden.
- The easiest way to view properties if they do not appear in the UI is by accessing the XML file for the page properties. For example, the XML for the above path is <http://192.168.168.110/@api/deki/files/9/properties>.