hosting

POST /v1/sites/{siteId}/protection/directories/remove

Take the password off a folder on a site.

Ҳамаи нуқтаҳои ниҳоии hosting

Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати sites.view бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/protection/directories/remove \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "directory": <string> }'

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди API-и фаъол иҷро мекунад, то шумо посухи воқеиро бубинед. Ин нуқтаи ниҳоиро дар консоли API кушоед

Тафсилот

Removes the folder's HTTP password. Everything in it becomes publicly readable again the moment this returns, so the client names the folder back before calling. ⛔ A `POST` to a `/remove` sub-path rather than a `DELETE` with the folder in the URL, and the folder travels in the **body**: a directory contains slashes, and a percent-encoded `/` inside a path segment is rejected or silently decoded by enough proxies that it is not a contract worth betting a security control on. The whole protection state comes back, so the card re-renders from the server's answer. `404` for a site with no vendor hosting package. Requires `sites.view` and `sites.panel_access`.

Параметрҳо

НомНамудТалаб карда мешавадИн чӣ аст
siteId (path)UuidБалеSite ID (UUIDv7).

Ҷисми дархост

НомНамудТалаб карда мешавадИн чӣ аст
directorystringБалеThe folder, exactly as `SiteProtection.directories` reports it. Normalised the same way on both sides, so the folder that is unprotected is the one that was named.

Ҷавоб

НомНамудТалаб карда мешавадИн чӣ аст
countriesstring[]БалеThe countries in the rule, as ISO 3166-1 alpha-2 codes.
countries_allow_onlybooleanБале⛔ `true` means `countries` is an **allow**-list: only those countries reach the site. Its own field rather than a mode string, because inverting it inverts who can reach the cus…
blocked_addressesstring[]БалеThe blocked addresses and CIDR ranges, canonicalised — what is here is what is in force, not what was typed.
visitor_blocking_permittedbooleanБалеWhether the package type permits blocking visitors at all. One flag governs both lists.
hotlink_configuredbooleanБалеWhether any hotlink rule exists. ⛔ `false` means *no rules have been set up* — **not** "protection is on with no allowed hosts", which would read as a site blocking everybody.
hotlink_allow_directbooleanБалеWhether a request with no referrer is allowed through. **Null** when the vendor did not state it — distinct from `false`, because a toggle rendered from an unknown lies about th…
hotlink_allowed_hostnamesstring[]БалеThe sites permitted to embed these files.
hotlink_redirect_urlstringБалеWhere a refused request is sent instead, or `""` when it is simply refused.
hotlink_extensionsstring[]БалеThe file extensions the rule covers, normalised without a leading dot.
hotlink_permittedbooleanБалеWhether the package type includes hotlink protection.
directoriesSiteProtectedDirectory[]БалеThe password-protected folders. ⛔ Read from a vendor field that documents `null` as *"the request could not complete"* — the opposite of "nothing is protected" — so an unreadabl…
password_protection_permittedbooleanБалеWhether the package type includes password-protected directories.
malware_scan_permittedbooleanБалеWhether the package type includes the vendor's malware scan — the capability behind `scanSite` on this deploy target.

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

401 · 403 · 404 · 409 · 422 · 429 · 503