solid / solid/specification

Precedence of response codes

Open
#146 5 comments 0 reactions 1 assignee View on GitHub

@csarven is already working on this.

Since Oct 19, 2022.

doc: Protocol status: Nominated topic: resource access
Dominant language
HTML
Stars
563
Forks
108
Avg merge
4d 13h
Merged PRs (30d)
3

Description

Consider, for example the request:

PUT /test-put-bc/dahut-bc.ttl
Authorization: Bearer SoOP3RS1krIT
If-None-Match: *
User-Agent: libwww-perl/6.36
Content-Type: text/turtle
Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel="type"

@prefix dc: <http://purl.org/dc/terms/>.
<> dc:title "Container Interaction Model"@en .

If the resource already exists, there are two different reasons why this request should fail:

  • It should fail with a 409 because ldp:BasicContainer is inconsistent with that the request URI does not end with a /.
  • It should fail with a 412 because it failed the precondition set by the If-None-Match: * header.

In such cases, should we express what should be checked first, IOW, what error message the client should see in every case, or should we leave that up to implementations?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.