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
An easy way for client-side Solid apps to get data into a user's dataspace. (I ran into this limitation when implementing a 'Save to Pod' bookmarklet).
ACL Interaction:
Copying from a non-LDP public Web resource to a container:
A COPY operation requires that the authenticated user has Write access to the destination container.
Copying FROM an LDP container to an LDP container:
A COPY operation requires that the authenticated user has Read access on the source container, and Write access on the destination container.
Interfacing with actual WebDAV servers:
Out of scope for the moment. We just need this as a convenience method to move to and from Solid servers.
To Do:
implement COPY verb on the server side, on ldnode
add a helper method to solid.js
The text was updated successfully, but these errors were encountered:
* Implement COPY verb support
Implements issue solid/solid#49, adds support for an
HTTP Copy verb that allows importing an external resource to a given Solid destination.
* Change the acl check for COPY to Write
* Extract LDP copy logic to ldp-copy module, per Nicola's request
Add limited support for the WebDAV COPY method. (There is currently no easy way to transfer files from the client side from one URL to another.)
Enables:
ACL Interaction:
Copying from a non-LDP public Web resource to a container:
A COPY operation requires that the authenticated user has Write access to the destination container.
Copying FROM an LDP container to an LDP container:
A COPY operation requires that the authenticated user has Read access on the source container, and Write access on the destination container.
Interfacing with actual WebDAV servers:
Out of scope for the moment. We just need this as a convenience method to move to and from Solid servers.
To Do:
ldnode
solid.js
The text was updated successfully, but these errors were encountered: