snapd unexpected HTTP status code 403
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snap Store Server |
Fix Released
|
Undecided
|
William Grant | ||
Bug Description
snapd 2.60.3 (log emitted prior to retrieving that version) still claims not expecting what the store keeps doing:
snapd.service snapd[1300]: stateengine.go:149: state ensure error: cannot decode new commands catalog: got unexpected HTTP status code 403 via GET to "https:/
Maybe the server could signal many different, but all expected status (e.g. 429, 503, 529) thus allowing the client to add client-
* this is temporary, will retry after [interval]
* this is server-side, check https:/
* this is you exceeding a rate limit, see LP: #1710022
This forum post appears to hint at a fix in that direction being live:
https:/
see also LP: #1950156
| William Grant (wgrant) wrote | #1 |
| Changed in snapstore-server: | |
| assignee: | nobody → William Grant (wgrant) |
| status: | New → Fix Released |
We usually return 429 in the names ratelimiting situation, but had missed one case which was still a 403. That's fixed now -- reply here if you see something like that again!