I’m getting this error message when making a call to the nfs file api. The content of the request is as follows:
Generalhttp://localhost:8100/nfs/file/test.txt/false
Response Headers
Request Headers/
Exact response is:
I can use the auth endpoint without problem but all calls to nfs/directory and nfs/file gives a similar error. The version of the launcher is v0.5.1.
Anyone’s got a similar problem?
On a side note, is maidsafe.readme.io the official api doc? Is it up to date?
The docs at readme.io aren’t up to date yet. This RFC houses the 0.5 spec to follow.
Looks to me like you’re missing the folder spec (app or drive) ahead of the file location (corresponding to the older is public that was on the end of the api).
if( metadata )
{
payload.headers.Metadata = metadata;
}
return fetch( url, payload )
.then( (response) => {
return checkBooleanResponse( response );
});
};
export const createOrUpdateFile = function( token, filePath, dataToWrite, dataType = 'text/plain', dataLength, metadata, isPathShared = false )
{
return getFileMetadata( token, filePath, isPathShared )
.then( headers =>
{
return deleteFile( token, filePath, isPathShared )
.then( success =>
such that the API request should look more like:
http://localhost:8100/nfs/<app or drive>/file/test.txt
I was running into the same problems before trying this.
3 Likes
Thanks, it works now. I like how the POST, GET and DELETE are now more alike, it made my code much cleaner.
2 Likes
cretz
July 11, 2016, 3:28pm
4
Yes! It’s now looking like WebDAV and following HTTP standards better. That was the goal.
2 Likes