Skip to content

Specify create Target Not Found as 404 - #241

Open
ebremer wants to merge 2 commits into
mainfrom
create-target-not-found
Open

Specify create Target Not Found as 404#241
ebremer wants to merge 2 commits into
mainfrom
create-target-not-found

Conversation

@ebremer

@ebremer ebremer commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

addresses: #87

Replace the untestable MUST-unless 404 sentence with atomic create failure rules and map Target Not Found to 404.
Unauthorized requests remain 401 or 403, with MAY 404 to hide existence.
**Behavior:**

* **Identity generation:** The server determines the final identifier (URI) for the new resource. If an identity hint was provided, the server attempts to incorporate it while ensuring uniqueness and validity within the <a>container</a>. If no hint is provided, the server generates a unique identifier.
* **Identity generation:** The server determines the final identifier (URI) for the new resource. If an identity hint was provided, the server attempts to incorporate it while ensuring uniqueness and validity within the <a>container</a>. If no hint is provided, the server generates a unique identifier. An identity hint is a suggested identifier, not a <a>containment</a> path. The server MUST NOT create intermediate <a>containers</a> in order to honor an identity hint.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that hint was there before this PR. I wonder if we should talk about any hinting at all in the core spec and leave it to outcomes from

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants