Test a proxy configuration without saving it
POST/config/proxy/validate
Merges the supplied fields over the stored configuration in memory, then sends an HTTP HEAD request through that proxy to a test URL and reports whether a 2xx response came back. Nothing is saved. The body has the same fields and rules as PATCH /config/proxy. A body that includes protocol, host or port but omits auth (or sends an empty auth) is tested without the stored credentials. A body containing only verify_ssl keeps them.
A failed connection test still returns HTTP 200 with success: false.
Required role: admin or superadmin.
Request
Responses
- 200
- 401
- 403
- 422
Result of the connection test.
No token, or the token is invalid or expired. The body is {message}: No auth token provided when no token is sent, otherwise the token check's message (jwt expired, jwt malformed, invalid signature, invalid token, jwt signature is required). Send Authorization: Bearer <token> exactly: the server drops the first seven characters of the header and reads the rest as the token, so a different scheme or an extra space fails. If Authorization is absent, the server reads a token field in the body, then a token query parameter, then x-access-token. Routes that validate query fields reject ?token= with 400 InvalidQuery.
The token's role is not allowed for this operation, or the token's scopes exclude the route
(Scope not allowed by token).
Invalid proxy configuration (same messages as PATCH /config/proxy).