hosting
POST /v1/sites/{siteId}/protection/directories/remove
Take the password off a folder on a site.
Ìfàṣẹ́pọ̀
Fi bọ́ọ̀lù (bearer token) ranṣẹ gẹ́gẹ́ bí kọ́kọ́rọ́ API. Kọ́kọ́rọ́ náà gbọ́dọ̀ ní ìyọ̀ǹda sites.view; a ó kọ̀ ọ́ silẹ pẹlu 403, kii ṣe 404, ti kọ́kọ́rọ́ náà kò bá ní i.
Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.
Gbiyanju rẹ
Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.
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> }'Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API
Àwọn kúlẹ̀kúlẹ̀
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.
Àwọn ìpìlẹ̀
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
siteId (path) | Uuid | Bẹẹni | Site ID (UUIDv7). |
Akoonu ibeere naa
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
directory | string | Bẹẹni | 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. |
Idahun
| Orúkọ | Iru | Tí a nílò | Kini o jẹ |
|---|---|---|---|
countries | string[] | Bẹẹni | The countries in the rule, as ISO 3166-1 alpha-2 codes. |
countries_allow_only | boolean | Bẹẹni | ⛔ 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… |
blocked_addresses | string[] | Bẹẹni | The blocked addresses and CIDR ranges, canonicalised — what is here is what is in force, not what was typed. |
visitor_blocking_permitted | boolean | Bẹẹni | Whether the package type permits blocking visitors at all. One flag governs both lists. |
hotlink_configured | boolean | Bẹẹni | 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_direct | boolean | Bẹẹni | 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 the… |
hotlink_allowed_hostnames | string[] | Bẹẹni | The sites permitted to embed these files. |
hotlink_redirect_url | string | Bẹẹni | Where a refused request is sent instead, or "" when it is simply refused. |
hotlink_extensions | string[] | Bẹẹni | The file extensions the rule covers, normalised without a leading dot. |
hotlink_permitted | boolean | Bẹẹni | Whether the package type includes hotlink protection. |
directories | SiteProtectedDirectory[] | Bẹẹni | 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 unreadable… |
password_protection_permitted | boolean | Bẹẹni | Whether the package type includes password-protected directories. |
malware_scan_permitted | boolean | Bẹẹni | Whether the package type includes the vendor's malware scan — the capability behind scanSite on this deploy target. |
Awọn aṣiṣe ti ibudo ipari yii le da pada
401 · 403 · 404 · 409 · 422 · 429 · 503