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
If you create C/R and C/ gets created on the fly (transparently), then the information about whether C/ existed beforehand stays more hidden, not less hidden?
Reopening the issue as it was closed by a non-CG member at the time, without CG's consent. The last useful revision in #139 (comment) is below, before the comment was erased.
when it does not want to acknowledge whether a resource exists
In #68, the current resolution is to automatically create intermediate containers as needed when a deeper document is created through PATCH (and perhaps other methods). In that case, success or failure of that operation might leak information in case 2 above.
GitHub's ToS allow users to reference and reuse publicly available comments within GitHub (see Section D.5). And, the Solid GitHub org operates under an MIT license, promoting open collaboration and transparency. Additionally, as part of the Solid CG, contributions fall under the W3C Community Group CLA, which permits broad reuse within the community.
RubenVerborgh
changed the title
Does recursive container creation leak information?
[Use of copyrighted material without permission or consent]
Feb 19, 2025
No description provided.
The text was updated successfully, but these errors were encountered: