Old Release

This documentation covers an old version of Fedora. Looking for another version? See all documentation.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


When referencing content hosted outside of the repository, you can create an empty binary to act as a placeholder for the external content, specifying the URL of the external content.

Instead of supplying the binary in the body of the request, you provide a Link header which uses the rel="http://fedora.info/definitions/fcrepo#ExternalContent" and specifies where to get the resource and how to handle it.

Link: <http://example.org/some/content>; rel="http://fedora.info/definitions/fcrepo#ExternalContent"; handling="proxy"; type="image/tiff"


The Fedora API specifies 3 methods of handling external content

  1. copy - Copy the binary from the provided URI and then treat it as a normal internal LDP-NR.
  2. redirect - On requests for the LDP-NR provide a redirect (302 Found or 307 Temporary Redirect) to the external URI.
  3. proxy - On requests for the LDP-NR proxy the request through the Fedora server the client with the same interaction as an internally stored LDP-NR.

The External Content Link also allows for a type= option. This is the content type that MUST be used by the server if provided.

If type= is omitted, then the server attempts to determine the Content-Type.

If the external URI has a file prefix (ie. local disk storage) then application/octet-stream is returned.

If the external URI has a http prefix then a HEAD request is made to the remote server to retrieve the Content-type header, if this header is not returned the resource cannot be added to the repository.

  • No labels