getSolidDatasetWithAcl function always logs 404 error

Hello everyone, I have a small problem:
getSolidDatasetWithAcl always logs error when given a dataset that doesn’t have acl attached to it yet.
Judging from the error itself it seems like inside this function there is a call that tries to get the provided dataset’s acl and because it doesn’t exist it would log the 404 error. Is there a way to suppress it?
Note: the function does work and it gives the dataset back, it’s the error message that bothers me.



I believe that’s your browser logging the network error, not something we can control; The SDK cannot know whether or not a resource exists until it requests it, hence, some percentage of requests will be network errors, but as long as they don’t throw you should be fine.


For Chromium, there seems to be some work into the direction of moving these logs out of the console (124534 - chromium - An open-source project to help move the web forward. - Monorail). I don’t know about other browsers.

But yeah, currently this is not up to the developers, but to the browser

1 Like