Type: Feature Request
Affects Version/s: None
Fix Version/s: None
Content Service stores Web Content (Text/url) in a similar way that other Resource types are stored: filepath/name as id and a cryptically named file in the filesystem.In the text/url case, he contents of the file consists of a url. (there might be more that is added there in some cases)
When accessed thru the rest api, files, other mime-types, such as x-application/pdf or somesuch, the contents of the file in the filesystem is passed back in the response.
With text/url types, though, the browser making the request is redirected to the url taken from the contents of the file.
The purpose is obviouslyt focused on returning the information (educational) and not documenting citations etc.
For archival, documentation, etc however it makes sense to have some ability retrieve just the url.
Example of REST call to retrieve a text/url Content Resource:
[The picket fencing in the url ('\/\/') is how json output from api formats the url's... requests in the format are still correctly handled]
File contents: http://www.youtube.com/playlist?list=PL9364A8FEB926E4AB
S. Swinsburg suggested "It would be worthwhile exploring a stripping of the access prefix to get just the URL for those types."