Running price on a domain that is not on the account:
$ sweb domains price amilima.ru
REGISTRATION PRICE —
REGISTER AVAILABLE yes
TRANSFER AVAILABLE —
registration price — Нет доступа к домену
transfer available — Нет доступа к домену
This is the designed behaviour: priceForRegistration and priceForTrasfer only
answer for a domain already on the account, which the command's Long help states.
The three checks are independent and the refusals are reported, as intended.
The problem is the wording. Нет доступа к домену is the raw upstream message and
reads as a token/permission failure, so the first reading is "my credentials are
wrong" rather than "this domain is not on my account". The message also arrives in
Russian in an otherwise English interface. It cost a real misdiagnosis.
Worth noting for triage: upstream is inconsistent with its own spec.
api-spec/openrpc/domains.json documents priceForRegistration as
"Стоимость регистрации домена" taking only domain, with no ownership
precondition — yet the gate exists, so the method answers only once the answer no
longer matters. priceForTrasfer has the same shape. There is no zone-pricelist
method to fall back on, and getAvailablePackages is not a pure read (it adds the
package to the account on a hit), so it cannot be used speculatively.
Options, not yet chosen:
- translate the known refusal into an explicit note, e.g.
domain is not on your account — SpaceWeb prices only domains you already own;
- detect ownership first and skip the two calls that are guaranteed to fail,
trading two round-trips for one;
- leave the calls, keep the raw message as a detail, and lead with the check that
does answer (REGISTER AVAILABLE).
Running
priceon a domain that is not on the account:This is the designed behaviour:
priceForRegistrationandpriceForTrasferonlyanswer for a domain already on the account, which the command's
Longhelp states.The three checks are independent and the refusals are reported, as intended.
The problem is the wording.
Нет доступа к доменуis the raw upstream message andreads as a token/permission failure, so the first reading is "my credentials are
wrong" rather than "this domain is not on my account". The message also arrives in
Russian in an otherwise English interface. It cost a real misdiagnosis.
Worth noting for triage: upstream is inconsistent with its own spec.
api-spec/openrpc/domains.jsondocumentspriceForRegistrationas"Стоимость регистрации домена" taking only
domain, with no ownershipprecondition — yet the gate exists, so the method answers only once the answer no
longer matters.
priceForTrasferhas the same shape. There is no zone-pricelistmethod to fall back on, and
getAvailablePackagesis not a pure read (it adds thepackage to the account on a hit), so it cannot be used speculatively.
Options, not yet chosen:
domain is not on your account — SpaceWeb prices only domains you already own;trading two round-trips for one;
does answer (
REGISTER AVAILABLE).