Subpath for anything endpoint
**OpenAPI Documentation Handler for `/anything/*path`**.
This function exists solely to generate the correct OpenAPI documentation
for requests to /anything/{path:.*} (e.g., /anything/foo/bar).
The actual requests to these wildcard paths are handled by anything_handler.
This separation is necessary due to current limitations in utoipa regarding
the generation of OpenAPI specs for handlers that serve both a fixed path and a wildcard path.
Path Parameters:
path: The subpath captured by the wildcard (e.g., “foo/bar”).
Responses:
200 OK: Echoes request details for the subpath.- Note: This handler, if ever called directly, returns
501 Not Implemented.
Path Parameters
Response
200 application/json
Response
Echoes request details for subpath
Path Parameters
Handles DELETE requests to `/delete`.
Echoes back the request’s method and headers. If a JSON body is provided,
it will also be echoed. Otherwise, the body in the response will be null.
HTTP Method:
DELETE
Request Body:
Payload(optional): A generic JSON object.
Responses:
200 OK: Returns a JSON object containing method, headers, and body (if provided).
Body
application/json
Body
Request payload wrapper for POST, PUT, PATCH, and DELETE handlers.
This newtype wraps a serde_json::Value to accept arbitrary JSON bodies
in requests that support request bodies.
Response
200 application/json
Response
Echoes request details, body is null if not provided
Body
Lists all available API endpoints provided by this server.
Returns a JSON array of EndpointInfo objects, each describing an endpoint’s
path, HTTP method, and a brief description.
HTTP Method:
GET
Responses:
200 OK: Successfully returns the list of endpoints.500 Internal Server Error: If there’s an issue serializing the endpoint data.
Response
200 application/json
Response
Lists all available API endpoints
Represents information about an API endpoint.
A brief description of the endpoint’s purpose.
Example:Echoes request details for GET.
The HTTP method of the endpoint (e.g., “GET”).
Example:GET
The path of the endpoint (e.g., “/get”).
Example:/get
Handles GET requests to `/get`.
Echoes back the request’s method and headers as a JSON object.
HTTP Method:
GET
Responses:
200 OK: Returns a JSON object containing the method and headers.
Response
200 application/json
Response
Echoes request details (includes a tls object over HTTPS)
Handles HEAD requests to `/get`.
Responds with the same headers as a GET request to /get, but with no body.
This is typically used to check if a resource exists or to get its metadata
without transferring the entire content.
HTTP Method:
HEAD
Responses:
200 OK: Returns an empty body with appropriate headers.
Response
200
Response
Responds with headers for GET query