Skip to content

Servers responding to request targets using the asterisk-form or the origin-form #356

@csarven

Description

@csarven

While the Solid Protocol requires servers to conform to RFC 7230 and RFC 7231, there may exist Solid server instances that cannot receive requests using the asterisk-form or a particular absolute-path (and path segments in lower hierarchy) as target.

It is important to consider whether any of the following requirements should be included in the Solid Protocol:

  • Servers MUST respond to request targets using the asterisk-form (RFC 7230).

  • Servers MUST respond to request targets using the origin-form (RFC 7230).

The first requirement is relevant for communication options: OPTIONS *. If servers cannot respond to requests using the asterisk-form as target, the following requirement either needs to be removed:

Servers MAY include the HTTP Accept-Patch, Accept-Post and Accept-Put headers in the response of a OPTIONS * request.

or the requirement for those Accept- headers should be in the response of OPTIONS for authorized requests.

The second requirement is relevant when responding to specific resources, and perhaps most importantly whether server can respond to request target: /.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions